External risk intelligence

BuddyPress Plugin Remote Code Execution Vulnerability

CVE advisorySeverity: CRITICAL (CVSS 9.8)

CVE-2026-120539

The vulnerability affects a WordPress plugin which is inherently designed to be deployed as a public-facing web application. Since the vulnerability is unauthenticated and triggered by a standard GET request, it is reachable by any public user accessing the website.

Remote Code Execution

Halo Surface Signal: 4 out of 5 — likely to be public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

A critical vulnerability has been identified in a WordPress plugin that could allow unauthenticated attackers to execute arbitrary code on your server. This issue stems from how the plugin processes website requests and could be triggered remotely. The main concern is confirming if this specific plugin combination is active on your WordPress sites.

  • Plugin allows unauthorized code execution remotely.
  • Critical vulnerability affects public-facing websites.
  • Confirm if this plugin combination is active.

Attack Path

How an attacker could exploit the issue

An unauthenticated attacker can reach the vulnerable component by sending a specially crafted GET request to a WordPress site that has specific plugins active. The attacker-controlled data in the URL is then processed unsafely by the vulnerable plugin, allowing arbitrary code execution on the server.

  • Requires specific plugins to be active.
  • Triggered via a malicious GET request.
  • Enables arbitrary code execution on server.

Live Threat

Current exploitation, exposure, and threat context

When the BuddyPress plugin, Paid Memberships Pro, and this plugin are all active, an unauthenticated attacker could execute arbitrary code on the server by sending a specially crafted GET request. This could impact the server's integrity and allow unauthorized actions.

  • Server-side code execution.
  • Triggered via a GET request.
  • Unauthorized server actions.

Operational Fix

Recommended remediation, mitigation, and detection steps

This critical vulnerability, affecting the Restrictions for BuddyPress plugin, enables unauthenticated remote code execution due to insecure handling of request URIs in PHP expressions. Given the plugin's typical deployment in WordPress environments, the initial step for responsible teams—likely including application owners, infrastructure teams, and security operations—is to identify all instances of the affected plugin. Subsequently, assess the reachability and business criticality of these installations to prioritize remediation efforts, involving coordination with the vendor or implementation of temporary mitigations if immediate patching is not feasible.

  • Application and infrastructure teams own the issue.
  • Verify plugin presence and reachability first.
  • Plan remediation based on exposure and criticality.

Supplementary metadata

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Frequently asked questions

What is the Restrictions for BuddyPress plugin?

It is an add-on for WordPress websites that helps site administrators control access to BuddyPress community features. It is designed to work alongside BuddyPress and the Paid Memberships Pro plugin to manage member restrictions based on subscription levels or profile settings.

What does CWE-95 mean for CVE-2026-120539?

CWE-95 refers to Improper Neutralization of Directives in Dynamically Evaluated Code, often called 'eval injection.' In this CVE, the plugin takes parts of a website's web address, puts them into a command, and runs that command as code. This lets an attacker use the web address to force the server to run unauthorized commands.

How is this vulnerability triggered?

An attacker sends a specific GET request—the same kind of request your browser makes to load a page—containing a malicious string in the URL. Importantly, the attacker does not need to log in to the site, and the code runs automatically because the plugin processes these requests before checking if a user has permission to be there.

Is my site at risk according to Halo Surface Signal?

Yes, if you use these plugins. Halo Surface Signal identifies this as a highly reachable vulnerability because it affects public-facing web applications. Since the plugin is meant for use on the open internet and the flaw is triggered by a standard web request, any site running the vulnerable combination is accessible to external actors.

What should I do to secure my site?

First, confirm if you are running the Restrictions for BuddyPress plugin alongside BuddyPress and Paid Memberships Pro. If you are, check your plugin management screen to determine which version is active. If you are on version 1.5.4 or older, prioritize updating the plugin immediately to resolve the unsafe code evaluation.

References