← All security briefings

Attention

Lazy Blocks (Custom Block Builder) before 3.0.0: unauthenticated code execution through REST routes (CVE-2026-127048)

Identifiers: CVE-2026-127048

Published
Last substantive change
Last verified

Last verified: . Attention items are due for re-verification within 72 hours.

Summary

CVE-2026-127048 affects the Lazy Blocks WordPress plugin, also listed as Custom Block Builder, in versions before 3.0.0. The plugin's REST permission checks return a value that WordPress treats as approval instead of a denial, so visitors with no account can reach routes that execute PHP code on the server. The flaw is fixed in version 3.0.0. That version dates back to 2022, so this is a newly published advisory about an old fix, not a new vendor release. Checked 16 November 2026.

Classification reason: Vendor fix available in version 3.0.0, published as a CVE by WPScan on 15 November 2026 following a 13 November 2026 notice. WPScan rates it 9.8 critical.

Impact

An attacker who can reach the plugin's REST routes needs no login to run arbitrary PHP on the site. Code execution at this level can lead to full site compromise, including new administrator accounts, hidden backdoors, and access to database contents.

Who is affected

Only WordPress sites running Lazy Blocks below 3.0.0 with the plugin's REST routes reachable are affected. Sites already on 3.0.0 or any later supported release are not affected by this specific issue. Separate fixes in later 4.x releases address different problems and do not change this version boundary.

Products and versions

Products and versionsAffectedFixed
Lazy Blocks / Custom Block Builder < 3.0.0 3.0.0

Exploitation evidence

Exploitation not established. The advisory describes unauthenticated code execution via misconfigured REST permission returns. No confirmed attacks are documented in the reviewed sources, and the exploit tag on the CVE reference is not evidence of active campaigns.

Sources: WPScan, Patchstack, CISA KEV

Actions

  1. Confirm the installed plugin slug and exact version in the WordPress plugins screen.
  2. If the version is below 3.0.0, update to a supported release compatible with your WordPress and PHP versions after taking a backup and testing on staging where possible.
  3. Verify the deployed version after updating and review recent administrator accounts, unexpected files, and scheduled tasks if the site was exposed for a long period.
  4. If you cannot update promptly, consider temporarily deactivating the plugin as containment, understanding this is not a substitute for the fix.

Unknowns

  • No in-the-wild exploitation has been established in the sources reviewed or the CISA catalog as of 16 November 2026.
  • The WPScan proof of concept is scheduled for release on 13 December 2026, so public technical detail is currently limited.
  • Whether a specific site was previously probed cannot be determined from the advisory alone.

Sources

  • WPScan · retrieved https://wpscan.com/vulnerability/b88c5a75-56ab-4722-8994-bbd6d97d2844/
  • WPScan / CVE Program · published · updated · retrieved https://cveawg.mitre.org/api/cve/CVE-2026-127048
  • Patchstack · retrieved https://patchstack.com/database/wordpress/plugin/lazy-blocks/vulnerability/wordpress-custom-block-builder-plugin-3-0-0-unauthenticated-rce-vulnerability
  • Plugin vendor / WordPress SVN · retrieved https://plugins.svn.wordpress.org/lazy-blocks/trunk/readme.txt
  • CISA KEV · retrieved https://www.cisa.gov/sites/default/files/feeds/known_exploited_vulnerabilities.json

Change history

  1. — Published: Briefing published 16 November 2026 after reviewing the WPScan notice of 13 November 2026, the CVE record of 15 November 2026, and the vendor changelog.

Subscribe: RSS feed · JSON Feed · Feed format and fields