The Custom Block Builder WordPress plugin before 3.0.0 does not properly deny unauthorised requests to its REST
Source GCVE Database
Not known to be exploited : upgrade to 3.0.0 soon.
Data as of 15 Nov 2026, 10:38 UTC
Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD
Thin evidence
One scorer or none- Patch
- Available – fixed in 3.0.0
Exploitation evidence
Disclosed: evidence found.
CVE published 15 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 14 Nov 2026.
What to do
Upgrade Custom Block Builder (WordPress plugin) to 3.0.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Custom Block Builder | Affected
| Fixed in
|
AI-suggested
If you cannot patch yet, it is recommended to disable or remove the Custom Block Builder plugin if it is installed and running a version prior to 3.0.0 to prevent exploitation.
Description
The Custom Block Builder WordPress plugin versions before 3.0.0 contain a vulnerability where unauthorized requests to its REST API routes are not properly denied. This occurs because the plugin's permission checks return a non-error response that WordPress interprets as authorization granted. As a result, unauthenticated users can execute arbitrary PHP code on the server.