Security alerts · November 21, 2026

Restrictions for BuddyPress WordPress plugin flaw lets unauthenticated attackers run code on the server

The Restrictions for BuddyPress plugin up to and including version 1.5.4 has a critical flaw rated CVSS 9.8. An unauthenticated attacker can run their own code on the server with a single request if BuddyPress and Paid Memberships Pro are also active. Update to version 1.5.5.

What happened

CVE-2026-120539 affects the Restrictions for BuddyPress plugin for WordPress, developed by SeventhQueen. The plugin is used to restrict access to content on community websites built with BuddyPress.

The flaw lets an attacker run arbitrary code on the server without logging in at all. The developer fixed it in version 1.5.5, published on GitHub on November 12, 2026, with the note “Update immediately”. The entry appeared in the US National Vulnerability Database (NVD) on November 21, 2026, with the severity score assigned by Wordfence, a company focused on WordPress security.

No one has confirmed active exploitation so far. The flaw is not in the CISA KEV catalog, and the European vulnerability database EUVD (entry EUVD-2026-131988) does not report exploitation. However, the attack is simple and the technical description is public, so you should expect attackers to take an interest.

Why it is dangerous

This is a code injection flaw (CWE-95, “eval injection”). According to the NVD description, the plugin took part of the web address sent by the visitor, placed it inside a piece of PHP code and then ran that code with the eval() function. Think of a receptionist who is handed a note by a stranger and simply does whatever it says.

Per NVD, the attacker needs no login or password, just a single ordinary request over the internet. The affected conditions are enabled by default and are evaluated before the plugin checks whether anyone is logged in, so no special configuration is required. WordPress’s built-in input escaping does not stop this attack, NVD notes.

Anyone who can run their own code effectively controls the site with the web server’s permissions. They can read wp-config.php with the database credentials, download user and member data, change site content, plant a backdoor, or use the server as a stepping stone to other systems on the same network or hosting account.

The CVSS score of 9.8 out of 10 was assigned by Wordfence and means critical severity: the attack works over the network, is simple, needs no login or user interaction, and threatens confidentiality, integrity and availability. The CISA KEV catalog lists flaws whose exploitation the US agency CISA has confirmed, and this one is not on it yet. An EPSS score, which estimates the likelihood of exploitation in the next 30 days, is not yet available.

Who is affected

This affects WordPress sites running the Restrictions for BuddyPress plugin in any version up to and including 1.5.4. According to NVD, all of the following must be true on the site:

  • Restrictions for BuddyPress (folder bp-restrict) version 1.5.4 or earlier
  • BuddyPress (active)
  • Paid Memberships Pro (active)

These are typically community and membership sites such as associations, clubs, learning portals or company communities with paid membership. They run on shared web hosting, a VPS or an in-house company server.

If BuddyPress or Paid Memberships Pro is not active, the flaw cannot be exploited according to the NVD description. Update the plugin anyway, because someone may enable those plugins later. Version 1.5.5 and sites without this plugin are not affected.

How to check if you are affected

The easiest way is to open the WordPress admin, go to Plugins, find Restrictions for BuddyPress and check the version number. The same list shows whether BuddyPress and Paid Memberships Pro are active.

If WP-CLI is available on the server, this command, run in the site folder, only lists plugin status and versions and changes nothing:

wp plugin list --fields=name,status,version | grep -Ei "bp-restrict|buddypress|paid-memberships-pro"

Without WP-CLI, you can read the version from the plugin file headers:

grep -i "Version:" wp-content/plugins/bp-restrict/*.php

If you manage several sites, for example on one hosting account, check each of them. The plugin folder may have a different name if it was installed manually.

How to fix it

SeventhQueen fixed the flaw in version 1.5.5. According to the release note, request data is no longer part of the evaluated code, and restrictions meant only for logged-in users are skipped for guests. Follow these steps:

  • Back up the site, both files and database.
  • Update Restrictions for BuddyPress to version 1.5.5 in the admin (Plugins) or with WP-CLI using wp plugin update bp-restrict.
  • If the admin does not offer the update, download version 1.5.5 from the developer’s GitHub releases page (seventhqueen/buddypress-restrict).
  • Confirm the new version and check that the site works.
  • Then move straight on to checking whether the site was compromised (section below).

The developer does not list any temporary workaround. If you cannot update right away, we recommend deactivating the plugin temporarily, keeping in mind that access restrictions on the site will stop working. A web application firewall (WAF) can reduce the risk but does not replace the update.

The flaw is not in the CISA KEV catalog, so CISA has not set a mandatory remediation deadline. With a score of 9.8 and no login required, that is no reason to wait. Treat the update as a priority.

What if you may already be compromised

Neither the developer nor NVD has published a list of indicators of compromise yet. According to the NVD description, however, the attack arrives as a GET request with an expression of the form {${...}} in the URL path. If the site ran a vulnerable version together with BuddyPress and Paid Memberships Pro, check at least the following:

  • web server access logs: GET requests containing {${ in the URL, often encoded as %7B%24%7B
  • new or unknown administrator accounts
  • PHP files in wp-content/uploads where they do not belong
  • modified core or plugin files and unknown scheduled tasks

This command searches the access logs, including older compressed ones, and changes nothing. The paths apply to Apache and Nginx on Debian and Ubuntu. On shared hosting, you will find the logs in your hosting control panel.

zgrep -iE '(\{|%7B)(\$|%24)(\{|%7B)' /var/log/apache2/access.log* /var/log/nginx/access.log* 2>/dev/null

These WP-CLI commands, run in the site folder, also only read data and change nothing:

wp user list --role=administrator --fields=ID,user_login,user_email,user_registered
find wp-content/uploads -name "*.php"
wp core verify-checksums
wp plugin verify-checksums --all

If you find anything suspicious, do not rush to delete it, so you keep the evidence. Contact your hosting provider or a security professional, change administrator and database passwords, and if personal data may have leaked, review your obligations under GDPR.

Sources

Articles are put together by an AI agent from public sources (vendors, CISA, ENISA, NVD, SK-CERT, NÚKIB), and version numbers and CVEs are checked against them automatically. Always confirm the steps in the vendor advisory before touching production.

← All alerts · RSS

Need help patching or checking your systems?

I can help you find out which systems are affected, update them safely and check whether an attacker already got in. Let us start with an initial consultation, which is deducted from the project price if we work together.