On this page (7 sections)
A critical vulnerability, CVE-2026-120539, has been published for the Restrictions for BuddyPress plugin for WordPress. According to the GitHub Advisory Database, all versions up to and including 1.5.4 let an unauthenticated attacker execute arbitrary code on the server with a single GET request.
If you run a WordPress community or membership site that combines BuddyPress, Paid Memberships Pro and this plugin, treat this as urgent. The advisory was published on November 21, 2026, and so far only one independent publisher covers it.
What happened
The plugin builds a PHP expression that includes the requested URL path and then runs it with eval(). The advisory and the NVD entry describe the result as unauthenticated remote code execution. The NVD text is the same wording as the advisory, so it is not a second, independent confirmation.
The advisory also references a 1.5.5 release on GitHub and a Wordfence vulnerability entry. The advisory itself lists patched versions as unknown, so verify the release notes before assuming 1.5.5 resolves the issue.
Technical details in plain terms
eval() takes a string and runs it as PHP code. That is dangerous whenever any part of the string comes from a visitor. This weakness class, CWE-95, is code injection: the application fails to neutralize input before dynamic evaluation.
Three details from the advisory make this case worse than a typical injection bug:
- The URL is placed inside a double-quoted PHP string. PHP interpolates such strings, so special syntax in the URL path is executed without the attacker needing to break out of quotes.
- WordPress' usual slashing of request data does not help, according to the advisory.
- The vulnerable conditions ship enabled by default and are evaluated before any logged-in check, so no plugin setup is needed and no account is required.
The CVSS vector reflects this: network attack, low complexity, no privileges, no user interaction, and high impact on confidentiality, integrity and availability. In practice, code execution in the web server context can mean data theft, a planted backdoor or a full site takeover.
Who is affected
The advisory says the site must have BuddyPress and Paid Memberships Pro active alongside this plugin. Sites that have only the Restrictions for BuddyPress plugin, without that combination, are not described as exposed by the advisory, but the safest course is still to update or remove an outdated copy.
Typical exposed sites are membership communities, paid forums and course sites that restrict BuddyPress content by membership level. Because no login is needed, being a small or obscure site is not protection.
How to check your exposure
This WP-CLI command, run from your WordPress root, lists installed plugins with their status and version. Look for BuddyPress, Paid Memberships Pro and the Restrictions for BuddyPress plugin, and check whether the last one is at 1.5.4 or lower.
wp plugin list --fields=name,status,version,updateIn the dashboard, the same information is under Plugins > Installed Plugins. The plugin's directory slug appears to be bp-restrict, but this is inferred from the WordPress plugin repository paths in the advisory references, not stated by the advisory itself.
You can also review known issues per plugin on our WordPress plugin vulnerability list and read how to tell if a plugin is vulnerable.
What to do now
- Take a full backup of files and database before changing anything.
- Run the plugin list command above and note the installed version of Restrictions for BuddyPress and whether BuddyPress and Paid Memberships Pro are active.
- If the version is 1.5.4 or lower, read the 1.5.5 release notes and update to the newest available release. The advisory does not formally list 1.5.5 as the fix, so treat the fix as unconfirmed.
- If you cannot confirm a fixed version, deactivate the plugin until one is available, and accept that restricted content may become visible while it is off. Review what that exposes first.
- Consider a firewall rule that blocks unusual characters in URL paths, but do not rely on it alone.
- Check for signs of compromise (see the next section) on any site that ran an affected version while publicly reachable.
- If you find signs of compromise, follow our website hacked guide and rotate WordPress, database and hosting credentials.
Before running the update command below, note two caveats: the fixed version is unconfirmed, and the slug bp-restrict is only inferred from repository paths. Confirm the exact plugin name in the output of the list command first, and substitute it if it differs. This command, run in the WordPress root, updates that plugin to the latest available release.
wp plugin update bp-restrictAfter updating, run the list command again and confirm the version is higher than 1.5.4.
Detection and monitoring
The advisory does not describe indicators of compromise, and the research reports no exploitation either way, so the following is general guidance rather than a known signature.
- Search web server access logs for GET requests with unusually long paths or paths containing curly braces and dollar signs, especially from a single IP.
- List PHP files changed recently in wp-content and the web root, and look for files you do not recognize, particularly in uploads and plugin directories.
- Review administrator accounts for users you did not create.
- Watch for unexpected outbound connections or sudden CPU spikes.
This read-only command is an nginx example. It prints up to 50 access-log lines where the request path contains a literal or URL-encoded opening curly brace. Replace the log path with the one on your system (Apache logs are usually in a different location). It will not catch braces written in other encodings, so treat a clean result as weak evidence.
grep -E 'GET [^ ]*(%7B|%7b|\{)' /var/log/nginx/access.log | head -n 50Matches are not proof of attack, since some legitimate URLs contain such characters, but repeated hits from one source deserve a closer look. Our guides on checking whether a website is hacked and what outside-in malware detection can and cannot see explain the limits of each approach.
What is still unknown
At publication, the research does not confirm a fixed version in the advisory, a public proof of concept, or whether the flaw is being exploited. It also shows no CISA Known Exploited Vulnerabilities listing. Because the flaw needs only one unauthenticated request and has a CVSS score of 9.8, it is reasonable to act as if attackers will take an interest once details spread. We will update this article if the advisory, the plugin developer or additional independent sources add detail.
Sources
This article is based on the public sources below. Details can change as vendors and researchers publish more; check the original advisories before acting on version numbers.
