Home › Vulnerabilities

Lazy Blocks plugin for WordPress Flaw CVE-2026-127048: Update Now

Published November 15, 2026 · Last updated November 15, 2026

WordPress CVE Critical Patch

CVE-2026-127048 is a critical flaw in Lazy Blocks, a WordPress plugin listed in the official plugin directory as "Custom Block Builder – Lazy Blocks." According to WPScan, unauthenticated visitors can use it to run their own PHP code on the web server. The fix is version 3.0.0.

The WordPress.org plugin directory reports more than 20,000 active installations. The flaw is not in the U.S. Cybersecurity and Infrastructure Security Agency's (CISA) Known Exploited Vulnerabilities catalog, and we found no public report of attacks using it.

Who is affected

Sites running Lazy Blocks (plugin slug lazy-blocks) at any version before 3.0.0. WPScan, the CVE Numbering Authority (CNA) that published the record, lists the plugin as "Fixed in 3.0.0."

What goes wrong

The CVE record says the plugin "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." WPScan classifies it as remote code execution (CWE-94, code injection). Running arbitrary PHP gives an attacker the same control over the site as its own code has.

Severity and who scored it

WPScan rates the flaw CVSS 9.8 (Critical) on its advisory page. The CVE record itself carries no CVSS score, and we could not get NVD's own assessment when we checked. So the 9.8 comes only from the CNA's advisory page.

The fix

Update Lazy Blocks to version 3.0.0 or later. The WordPress.org directory showed version 4.5.1 as current when we checked.

What to do

  • WordPress site owners and administrators: in the Plugins screen, check whether Lazy Blocks is installed and which version you run. If it is older than 3.0.0, update it now.
  • If you cannot update right away: deactivate the plugin until you can. This is general advice, not vendor guidance.
  • Hosting providers and agencies managing many sites: search your fleet for lazy-blocks versions below 3.0.0.

Timeline

  • November 13, 2026: WPScan publicly published the advisory.
  • November 15, 2026: CVE-2026-127048 published by WPScan.

Sources

  • WPScan advisory: https://wpscan.com/vulnerability/b88c5a75-56ab-4722-8994-bbd6d97d2844/
  • CVE record: https://www.cve.org/CVERecord?id=CVE-2026-127048
  • WordPress.org plugin page: https://wordpress.org/plugins/lazy-blocks/

Sources

General education only, not security advice. Facts checked against the sources above on the date shown.