# CVE-2026-127048: Lazy Blocks < 3.0.0 - Unauthenticated RCE

> Unauthenticated attackers can execute arbitrary PHP code via the plugin's REST routes; WordPress sites using Custom Block Builder should care.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Harmful if only installed:** No
- **Needs a specific call:** No
- **Fix available:** No
- **Published:** 15 Nov 2026
- **Updated:** 16 Nov 2026
- **Also known as:** GHSA-m4vj-2mv4-rv7p

## What is CVE-2026-127048?

CVE-2026-127048 is a critical missing authorization vulnerability in Custom Block Builder, published on 15 Nov 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-94 (Improper Control of Generation of Code)

## Which versions are affected by CVE-2026-127048?

An affected version is exposed as installed. No special setting or call is needed.


## How do I fix CVE-2026-127048?

No fix has been published for CVE-2026-127048 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-127048 being exploited?

There is no known exploitation of CVE-2026-127048 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-127048 and fix it if it is affected.

What it is: CVE-2026-127048 is a critical missing authorization vulnerability in Custom Block Builder, published on 15 Nov 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-127048 in the wild and no public exploit code.
Exposure: An affected version is exposed as installed. No special setting or call is needed.

Affected product: Custom Block Builder. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-127048/ (Markdown: https://insights.sbomify.com/CVE-2026-127048/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-127048
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-127048
- OSV: https://osv.dev/vulnerability/CVE-2026-127048

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-127048/
Summaries are generated and may contain mistakes; the official description above is the record.
