Critical 9.8
CVE-2026-120539
The Restrictions for BuddyPress plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 1.5.4 This is due to the plugin splicing the attacker-controlled request URI into a PHP expression inside a double-quoted string and evaluating it with eval(). Because PHP interpolates double-quoted strings, a payload of the form {${...}} in the URL path is executed during interpolation, so no quote breakout is required and WordPress' slashing does not mitigate it. This makes it possible for unauthenticated attackers to execute arbitrary code on the server with a single GET request. The affected conditions ship enabled by default and are evaluated before any logged-in check, so no plugin configuration is needed; the site must have BuddyPress and Paid Memberships Pro active alongside this plugin.
How scary is it?
updated 21 Nov 2026- Yes
Works without logging in1
No account and no user action needed (CVSS PR:N, UI:N).
- Yes
Reachable over the network1
Can be attacked remotely (CVSS AV:N).
- Yes
Proof-of-concept code is public2
1 GitHub proof of concept. GitHub proofs of concept are unvetted: some are fake or carry malware. No Exploit-DB entry or Metasploit exploit module on record.
- None known
Attacks seen in the wild
None reported that we know of.
- No
On CISA's exploited list3
Not in the catalog as of our last sync.
Scare-o-meter
Act this week
Serious and within reach of attackers. Schedule the fix this week.
- Low signal
- Routine patch
- Act this week
- Drop everything
Why: Reachable over the network with no login and no user action; CVSS 9.8.1 Read from the same rule that decides our alert emails.
Are you affected? only if all are true
You run seventhqueen Restrictions for BuddyPress in an affected version<= 1.5.4
The CVE record states no fixed release.
As published in the CVE record. A version outside these ranges is not a statement that it is unaffected: vendors sometimes understate a range, and distribution builds with backported fixes keep the upstream number.
See the affected products table · Source 1
An attacker can reach it over the network
CVSS attack vector: Network (AV:N). Reachable over the internet or any routable network.
Source 1
Read from the CVE record: affected versions and the CVSS vector. It narrows things down. It does not prove you are safe.
What to do
We hold no fix information for this CVE: no fixed release in the CVE record and no action text. See the references.
- CVSS
- 9.8Criticalscored by the publisher (CNA)
- Exploited in the wild
- Not knownUnvetted proof-of-concept code on GitHub; not in CISA KEV
- EPSS
- 2.2%chance of exploitation in the next 30 daystop 18% of scored CVEsFIRST score of 21 Nov 2026
- Fix
- Not stated by the vendorno fixed release in the CVE record
- Published
- 21 Nov 2026analysed here 21 Nov 2026
Summary
Triage
Executive summary (AI-written)
A high-severity vulnerability has been identified in the Restrictions for BuddyPress plugin for WordPress, potentially affecting all versions up to 1.5.4. This vulnerability allows unauthenticated attackers to execute arbitrary code on the server through a single GET request due to the improper handling of user input. Given the critical nature of this vulnerability and its ability to compromise WordPress sites, it poses a substantial risk to business continuity and data security, particularly for organizations relying on the BuddyPress and Paid Memberships Pro plugins. Without a patch currently available, organizations using this plugin should take immediate steps to assess their exposure to this vulnerability. It is essential for decision-makers to prioritize mitigating strategies, such as disabling the vulnerable plugin or implementing access controls, to protect their web assets from potential remote attacks, which could lead to data breaches and significant reputational damage.
Technical analysis (AI-written)
CVE-2026-120539 has been classified with a CVSS score of 9.8, indicating a critical risk associated with the vulnerability. The issue lies in how the Restrictions for BuddyPress plugin handles user-controlled input through a PHP expression evaluated with eval(). Specifically, the double-quoted string interpolation allows an attacker to execute arbitrary PHP code via a crafted URL, thereby compromising the server. The vulnerability is present in all versions up to and including 1.5.4, and crucially, it does not require any authentication, allowing the exploitation to be executed by unauthenticated users. The attack vector is straightforward, as it involves sending a specially crafted GET request to the WordPress server hosting the vulnerable plugin. This means that any site running BuddyPress in conjunction with the Paid Memberships Pro plugin is at risk, particularly if the Restrictions for BuddyPress plugin is enabled by default, which it is. The lack of mitigation strategies or available patches increases the urgency for organizations to address this vulnerability. From a technical standpoint, the vulnerability could lead to a complete takeover of the web server by allowing remote code execution with no conditions set for proper authentication checks. WordPress slashing does not effectively mitigate the risk either, as the PHP interpreter still processes the harmful payload within the evaluated string. Organizations should prioritize reviewing their installed plugins, especially the BuddyPress-related plugins, and consider deactivating the Restrictions for BuddyPress plugin until a patch is released. To mitigate risks associated with this vulnerability, organizations are advised to implement strict input validation where possible and enhance monitoring for unusual behavior on their servers. This includes establishing proper access controls, reviewing logs for unauthorized access attempts, and considering alternative solutions or configurations that do not rely on the vulnerable plugin. In the absence of a formal patch, a focus on reducing the attack surface by disabling the vulnerable plugin and implementing application firewall rules is essential to safeguard web assets against potential exploitation of CVE-2026-120539.
The summary, impact and action text on this page are written by our AI analysis pipeline, or taken from the NVD description when a CVE was imported from NVD. They are not the vendor's wording: check them against the sources.
Affected products
| Product | Affected versions | Vendor says fixed in |
|---|---|---|
| seventhqueen Restrictions for BuddyPress | <= 1.5.4Vendor says fixed in: not stated |
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.
Fix and mitigation
WAF and other mitigations
Can a WAF block it? Partly. The attack is delivered via a specially crafted HTTP GET request where the URL path includes a payload with {${...}} syntax that triggers code execution. This unusual pattern in the URL path can be detected and blocked by a web application firewall. A WAF rule can match URL path containing {${...}} sequences. No tracked WAF vendor has published a rule for this CVE yet, so you would write it yourself.
What a custom rule would match: URL path containing {${...}} sequences
Also consider: patch · custom WAF rule
Based on an AI reading of the CVE description, and no vendor rule found yet. We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.
Remediation steps (AI-written)
Step-by-step remediation is generated for accounts on the Max plan, for CVEs that match a technology in their stack. Add this technology to your stack to see the fix checklist.
Exploitation evidence
- CISA KEV catalog
- Not listed as of our last sync.
- Public exploit code
- Unvetted proof-of-concept code on GitHub: 1 GitHub proof of concept
GitHub proofs of concept
- LLCForge/CVE-2026-1205390 stars
Listed so you can judge urgency, not as a recommendation to run anything. GitHub “proofs of concept” are unvetted: some are fake or carry malware. Exploit-DB marks the entries its staff verified.
Timeline
- 21 Nov 2026First proof-of-concept repository on GitHub (unvetted)
- 21 Nov 2026CVE record last updatedsame day later
- 21 Nov 2026Publishedsame day later
- 21 Nov 2026Analysed by vulneraibility.comsame day later
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
| Metric | Value | What it means |
|---|---|---|
| Attack vector | NetworkReachable over the internet or any routable network. | Reachable over the internet or any routable network. |
| Attack complexity | LowRepeatable attack, no special conditions. | Repeatable attack, no special conditions. |
| Privileges required | NoneThe attacker needs no prior access. | The attacker needs no prior access. |
| User interaction | NoneNo victim action needed. | No victim action needed. |
| Scope | UnchangedImpact stays within the vulnerable component. | Impact stays within the vulnerable component. |
| Confidentiality | HighTotal data disclosure possible. | Total data disclosure possible. |
| Integrity | HighComplete modification possible. | Complete modification possible. |
| Availability | HighFull outage possible. | Full outage possible. |
Common questions
Is CVE-2026-120539 being exploited?
Not confirmed. CVE-2026-120539 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 2.2% probability of exploitation in the next 30 days.
How severe is CVE-2026-120539?
CVE-2026-120539 is rated Critical with a CVSS score of 9.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-120539?
Not known from our data. No patch reference has been recorded for CVE-2026-120539, which is not the same as no patch existing — a fix may have shipped without a tagged reference, or after this record was written. The vendor advisory is the only authority on whether a fix exists, and mitigations may be available regardless.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
References
7 references in the CVE record, grouped by the tags the record gives them.
Other links (7)
- wordfence.com /threat-intel/vulnerabilities/id/fab68c0b-2211-4cc4-a112-f0011f9d72ed?source=cve
- plugins.trac.wordpress.org /browser/bp-restrict/tags/1.5.4/admin/class-bp-restrict-pmpro.php#L187
- plugins.trac.wordpress.org /browser/bp-restrict/tags/1.5.4/admin/class-bp-restrict-pmpro.php#L184
- plugins.trac.wordpress.org /browser/bp-restrict/tags/1.5.4/includes/class-bp-restrict.php#L210
- plugins.trac.wordpress.org /browser/bp-restrict/tags/1.5.4/includes/class-bp-restrict.php#L172
- plugins.trac.wordpress.org /browser/bp-restrict/tags/1.5.4/admin/class-bp-restrict-admin.php#L213
Show 1 more
- github.com /seventhqueen/buddypress-restrict/releases/tag/1.5.5
Where the data on this page comes from
- CVE List (CVE.org): description, affected versions, references; CVE Terms of Use
- NVD: CVSS and CPE data
- FIRST EPSS: exploit probability and percentile
- PoC-in-GitHub: GitHub repositories that claim a proof of concept
Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.
Similar CVEs
Get CVEs like this by email. Join the free digest: the CVEs we flag as major, all CVSS 8.0 or higher, in up to three emails a day (sent at 05:00, 11:00 and 15:00 UTC). Matching alerts to the products you run needs an account, and accounts are invite-only during the beta.