Skip to main content
CVE-2026-120539VulnerabilityPublished

The Restrictions for BuddyPress plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-120539· Critical 9.8

Not known to be exploited · CVSS 9.8 Critical.

Data as of 21 Nov 2026, 07:15 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (Wordfence)CVSS 3.19.8
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 21 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 20 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
seventhqueenRestrictions for BuddyPressAffected
  • <=1.5.4
Fixed in–

AI-suggested

Until a fix is available, disabling or removing the Restrictions for BuddyPress plugin or the dependent plugins (BuddyPress and Paid Memberships Pro) can mitigate risk. Monitor official sources for updates and apply patches promptly once released.

Description

The Restrictions for BuddyPress plugin for WordPress versions up to and including 1.5.4 contains a critical remote code execution vulnerability. This flaw arises from unsafe use of eval() on attacker-controlled request URIs, allowing unauthenticated attackers to execute arbitrary PHP code via a crafted GET request. The vulnerability is exploitable without authentication and requires the presence of BuddyPress and Paid Memberships Pro plugins. No plugin configuration changes are needed to trigger the flaw.

References

Community reviews

Loading reviews…