CVE-2026-127048 in Custom Block Builder Plugininfo

Summary

by MITRE • 11/15/2026

The Custom Block Builder WordPress plugin before 3.0.0 does not properly deny unauthorised requests to its REST routes, as its permission checks return a non-error response that WordPress treats as granted, allowing unauthenticated users to execute arbitrary PHP code on the server.

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Analysis

by VulDB Data Team • 11/15/2026

The vulnerability in Custom Block Builder versions prior to 3.0.0 represents a critical failure in access control mechanisms within the plugin's REST API implementation. The core issue stems from an improper permission check logic where the function responsible for validating user privileges fails to return a standard WordPress error response when authorization is denied. Instead of returning a WP_Error object or a similar structure that signals rejection, the code returns a value that the WordPress framework interprets as successful authentication. This architectural flaw effectively bypasses security controls designed to restrict access to administrative functions based on user roles and capabilities.

From a technical perspective, this misconfiguration allows unauthenticated attackers to interact with sensitive REST endpoints intended for authorized administrators only. Because the permission check is circumvented without triggering an error state, the server proceeds to execute the requested operations as if the request originated from a legitimate administrator account. This specific failure mode aligns closely with CWE-284 Improper Access Control and CWE-732 Operator Permission Errors, highlighting a fundamental breakdown in verifying user identity before granting access to protected resources. The vulnerability is particularly severe because it does not require any form of authentication or session hijacking; the attack vector relies solely on crafting specific HTTP requests to the exposed REST routes.

The operational impact of this flaw is significant, as it enables Remote Code Execution (RCE) on the affected WordPress server. By exploiting these unprotected endpoints, an attacker can inject and execute arbitrary PHP code with the privileges of the web server process. This level of access allows for complete compromise of the underlying system, including the ability to read sensitive data such as database credentials, modify website content, install malicious plugins or themes, and potentially pivot to attack other systems within the network infrastructure. The ease of exploitation makes this a high-risk vulnerability that can be leveraged by automated scanning tools and script kiddies alike, leading to widespread compromise if left unpatched.

In terms of threat modeling, this vulnerability maps directly to MITRE ATT&CK techniques related to Initial Access via Web Applications and Privilege Escalation through improper permission checks. Attackers typically exploit such flaws during the initial intrusion phase by sending crafted requests that trigger the vulnerable code paths. The lack of proper error handling means that even sophisticated security monitoring tools might struggle to distinguish between legitimate administrative activity and malicious exploitation attempts, as both result in successful execution rather than blocked access logs.

To mitigate this risk, immediate action is required to update the Custom Block Builder plugin to version 3.0.0 or later, where these permission checks have been corrected to properly return error responses for unauthorized requests. Organizations should also implement Web Application Firewalls (WAFs) that can detect and block anomalous REST API traffic patterns associated with exploitation attempts. Regular security audits of custom plugins are essential to ensure that all endpoints adhere to WordPress coding standards regarding capability verification using functions like current_user_can or similar robust checks. Additionally, restricting access to the wp-admin directory via IP whitelisting for administrative interfaces provides an additional layer of defense against unauthorized API interactions.

Responsible

WPScan

Reservation

11/12/2026

Disclosure

11/15/2026

Moderation

accepted

CPE

ready

EPSS

0.00173

KEV

no

Activities

very low

Sources

Might our Artificial Intelligence support you?

Check our Alexa App!