External risk intelligence

WordPress Custom Block Builder PHP Code Execution

CVE advisorySeverity: CRITICAL (CVSS 9.8)

CVE-2026-127048

The vulnerability affects a WordPress plugin, which is typically deployed as a public-facing web application. Since the issue involves exposed REST routes reachable by unauthenticated users, the attack surface is commonly accessible via the public internet as part of the standard web application deployment.

Code Injection

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

This critical vulnerability in a WordPress plugin allows unauthenticated attackers to execute arbitrary code on affected servers by exploiting improperly handled requests to REST routes. The issue arises from insufficient permission checks, which could lead to a compromise of the underlying server.

  • Unauthenticated access can run harmful code.
  • It impacts public-facing websites.
  • Confirm relevance and assess exposure.

Attack Path

How an attacker could exploit the issue

An attacker could exploit this vulnerability by sending unauthenticated requests to the plugin's REST API routes. The plugin incorrectly permits these requests, allowing the attacker to execute arbitrary PHP code on the server, which could lead to a full site compromise.

  • Unauthenticated network access required.
  • Exploits exposed REST API routes.
  • Allows arbitrary code execution.

Live Threat

Current exploitation, exposure, and threat context

This vulnerability could allow unauthenticated users to execute arbitrary PHP code on the server when interacting with specific REST routes within the Custom Block Builder WordPress plugin. This occurs because the plugin's permission checks do not adequately deny unauthorized requests, leading WordPress to treat them as granted.

  • Arbitrary PHP code execution on server.
  • Unauthenticated REST route access.
  • Server compromise, data loss.

Operational Fix

Recommended remediation, mitigation, and detection steps

This vulnerability in the Custom Block Builder WordPress plugin impacts application owners and potentially infrastructure or platform teams responsible for the WordPress environment. The first practical step is to identify all WordPress instances, confirm their exposure and criticality, and then locate the specific owner for remediation planning.

  • Identify affected WordPress instances and owners.
  • Verify plugin reachability and business criticality.
  • Plan remediation based on risk and impact.

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 Custom Block Builder plugin?

Custom Block Builder is a WordPress plugin designed to help users create and manage custom content blocks within the WordPress block editor environment. It extends the platform's core functionality, allowing site administrators to build reusable UI components or layout elements without needing deep manual coding, making it a common tool for web developers and site maintainers.

What does CWE-94 mean for CVE-2026-127048?

CWE-94 refers to improper control of code generation or execution. In this context, it means the plugin fails to properly validate who is allowed to use its background processes. Because the permission checks are flawed, the system incorrectly interprets unauthorized requests as legitimate, allowing external users to inject and execute their own PHP commands on the server.

How can an attacker trigger this vulnerability?

An attacker triggers the vulnerability by sending specifically crafted requests to the plugin's REST API endpoints. Crucially, the attacker does not need an account or any prior credentials to perform these actions. Simply sending a request that the plugin fails to block is enough to initiate the unauthorized execution; standard, legitimate user interactions that do not target these specific REST routes do not trigger the flaw.

Is my website at risk from this CVE?

According to Halo Surface Signal, this vulnerability is classified as likely to be relevant because the plugin functions as a web application component. Since WordPress sites are typically deployed on the public internet, these REST routes are often reachable by anyone globally, meaning almost any public-facing site using the affected plugin versions is within the potential attack path.

How do I respond to this threat?

Begin by auditing your environment to locate all WordPress instances where the Custom Block Builder plugin is installed. Once identified, determine which sites are public-facing and assess their business importance. After cataloging these assets, prioritize them for updates or temporary disabling of the plugin to prevent unauthorized code execution while you plan a permanent resolution.

References