CVE-2026-120539 Security Alert: CRITICAL Vulnerability
Urgent: CVE-2026-120539 requires immediate attention.
· 7 min read
Executive Summary
CVE-2026-120539 is a critical remote code execution flaw in the Restrictions for BuddyPress WordPress plugin, affecting all versions up to and including 1.5.4. An unauthenticated attacker can trigger code execution with a single crafted GET request by abusing how the plugin evaluates the request URI with eval(). Because the payload is executed during PHP string interpolation, no quote breakout is required and WordPress slashing does not stop it.
This is especially urgent for solo developers and small teams because the vulnerable path is evaluated before any logged-in check and is enabled by default. The site must have BuddyPress and Paid Memberships Pro active alongside this plugin, but if that stack is present, assume the server is at risk until patched or disabled.
Immediate Action
- Upgrade immediately to the first fixed release of Restrictions for BuddyPress. TODO: confirm vendor patch version and deploy it now.
- If you cannot patch within minutes, disable the plugin and, if needed, temporarily deactivate the BuddyPress + Paid Memberships Pro combination that exposes the vulnerable path.
- Isolate the WordPress host from the internet if this site is business-critical and you cannot confirm remediation yet; at minimum, restrict admin access and monitor inbound requests.
- Check web logs for suspicious GET requests containing unusual path fragments such as
{${,eval-like payloads, or unexpected long encoded URI paths. - Rotate secrets after remediation if you see signs of compromise: WordPress salts, database credentials, API keys, SSH keys, and any deployment tokens.
- Review the vendor advisory and changelog: vendor advisory / release notes.
Affected Versions
restrictions-for-buddypress@<=1.5.4— vulnerablerestrictions-for-buddypress@1.5.5+— safe only if confirmed by vendor (TODO: verify fixed version)- Requires BuddyPress and Paid Memberships Pro active alongside the plugin
Resolution Guide
WordPress / PHP is the primary ecosystem here. There is no npm/pip/Maven package to update for this issue, but the commands below help teams standardize patching and hardening workflows.
# WordPress plugin update via WP-CLI
wp plugin update restrictions-for-buddypress
# If you need to disable immediately
wp plugin deactivate restrictions-for-buddypress
# Check installed version
wp plugin list --status=active | grep -i 'restrictions-for-buddypress'
# Search for the vulnerable eval pattern in the plugin files
grep -RIn --color=always 'eval\s*(' wp-content/plugins/restrictions-for-buddypress/
grep -RIn --color=always '\$_SERVER\[' wp-content/plugins/restrictions-for-buddypress/
# Docker: rebuild with the patched plugin or remove the vulnerable plugin layer
docker build --no-cache -t your-wordpress:patched .
docker run --rm -p 8080:80 your-wordpress:patched
# If using a prebuilt image, pin to a known-good tag
docker pull your-registry/wordpress-app:TODO_FIXED_TAG
# Linux package managers are not usually used for this plugin,
# but if your deployment bundles WordPress in a system image, update the site package:
sudo apt-get update
sudo apt-get install --only-upgrade wordpress
# or
sudo yum update wordpress
Hardening steps:
# Temporarily disable the vulnerable feature path by removing the plugin
wp plugin deactivate restrictions-for-buddypress
# Add a web server rule to block suspicious payload markers in the URI path
# Example for Nginx
location / {
if ($request_uri ~* "\{\$\{") { return 403; }
}
Code fix example for maintainers: remove eval() and avoid interpolating attacker-controlled URI data into PHP expressions.
// Vulnerable pattern (do not use)
eval("return \"$request_uri\";");
// Safer pattern: treat input as data, not code
$request_uri = $_SERVER['REQUEST_URI'] ?? '';
$sanitized = sanitize_text_field(wp_unslash($request_uri));
// Use allowlists / strict parsing instead of evaluation
if (!preg_match('/^[a-zA-Z0-9\/._-]+$/', $sanitized)) {
wp_die('Invalid request');
}
Detection & Verification
Check whether you are vulnerable:
# Confirm the plugin version
wp plugin get restrictions-for-buddypress --field=version
# If you do not have WP-CLI, inspect the plugin header
grep -RIn "Version:" wp-content/plugins/restrictions-for-buddypress/
# Look for the dangerous construct
grep -RIn --color=always 'eval\s*(' wp-content/plugins/restrictions-for-buddypress/
Check for exploit attempts in logs:
# Apache/Nginx access logs
grep -RIn --color=always '\{\$\{' /var/log/apache2/ /var/log/nginx/
# Search for suspicious long or encoded GET paths
grep -RIn --color=always 'GET .*%7B%24%7B\|GET .*\{\$\{' /var/log/apache2/ /var/log/nginx/
Verify the fix:
# After upgrading, confirm the version is above the vulnerable range
wp plugin get restrictions-for-buddypress --field=version
# Re-scan the plugin directory for eval usage
grep -RIn 'eval\s*(' wp-content/plugins/restrictions-for-buddypress/ || echo "No eval found"
# If you use a dependency/security scanner, re-run it
composer audit || true
npm audit || true
pip-audit || true
Risk and Impact
If exploited, an attacker can execute arbitrary PHP on the server as the web process user. That can lead to full site takeover, database theft, malware injection, spam redirects, credential harvesting, and lateral movement into adjacent services or cloud resources.
For small teams, the blast radius can be broad because a compromised WordPress host often stores API keys, SMTP credentials, backups, and deployment secrets. Even without signs of active exploitation, this should be treated as a same-day emergency patch.