A path query exposes the visibility limits around the bp-restrict WordPress plugin
Restrictions for BuddyPress uses the WordPress slug bp-restrict. CVE-2026-120539 affects versions through 1.5.4 and involves unauthenticated PHP code execution through request-URI interpolation in an eval() expression. The plugin directory says the current package includes a security fix for that class of issue.
For exposure research, a plugin path should be a stronger signal than a display name. I tested both on November 22, 2026, between 03:40 and 03:42 CST, with sub_type=all, page 1, and page size 1. http.body="/wp-content/plugins/bp-restrict/" returned 0. Without the trailing slash, /wp-content/plugins/bp-restrict also returned 0. http.body="bp-restrict" returned 104. title="BuddyPress" returned 66, and http.body="Restrictions for BuddyPress" returned 0.
What the result says
The exact path did not find a population in this index. That is a visibility result, not proof that no deployments exist. The plugin may enqueue assets from a different path, hide the directory, use a custom WordPress layout, or appear only after authentication.
The slug without the directory path found 104 matches. This is a weaker signal. "bp-restrict" can appear in a changelog, a vulnerability article, an admin page, or an asset filename. The BuddyPress title count is broader still and includes the platform, not necessarily this restriction plugin.
The honest conclusion is that a title-only or exact-path scan is insufficient. The next layer must be internal WordPress inventory, file-system verification, and version checking.
Review the plugin on controlled sites
For each site running the plugin, verify the version and update above 1.5.4. If a current fixed package is unavailable, disable the plugin until the site can be updated. Review the restriction-condition evaluation path, because the vulnerability is caused by executable string assembly rather than a simple permission flag.
Search access logs for plugin routes with encoded braces, unusual query strings, and PHP-like fragments in the URI. Inspect upload and cache directories for unexpected PHP files. Check new administrator accounts, modified themes, mu-plugins, cron entries, and outbound connections.
If code execution is suspected, preserve the web root and database before cleanup. Rotate WordPress salts, database credentials, API keys, and any integration secrets stored in the site. A WAF rule can reduce exposure during the patch window, but it should not be described as a fix for eval().
Build a reproducible exposure record
Keep the exact-path result at zero and the slug result at 104 separate. State the collection scope and the false-positive risk. Match the candidates to domains you own, then replace the external count with authenticated plugin inventory.
The query is still useful as a recurring check. If the exact path begins to return results, that is a new observation worth reviewing. If it remains zero, the absence should be reported as a field-scope limit, not as evidence that all WordPress sites are safe.
Next action
Start with internal WordPress inventory rather than treating the 104 slug matches as deployments. Confirm the plugin version, patch or disable it, and investigate any site with unexplained PHP files or request-URI activity. Preserve the zero exact-path result as a visibility finding and do not inflate it with broader BuddyPress counts.
Top comments (0)