WordPress security changelog
HIGH CVE-2026-1560 Deferred

Custom Block Builder – Lazy Blocks: Code execution

Custom Block Builder – Lazy Blocks is affected by code execution. Exploitation requires at least contributor-level access. Successful exploitation can run attacker-controlled code in the WordPress hosting account.

CVE / CNA score 8.8 CVSS 3.1 · security@wordfence.com
NVD score Pending NVD has not published its own CVSS assessment.
Component
Custom Block Builder – Lazy Blocks
Plugin slug
lazy-blocks
Affected
See vendor advisory
Safe version
See mitigation notes
Published
Feb 11, 2026
Weakness
CWE-94 — Improper Control of Generation of Code ('Code Injection')

This CVE was published Feb 11, 2026 and is one of 3 known issues for this plugin.

Update, patch or deactivate.

Update Custom Block Builder – Lazy Blocks to a release outside the affected range, or disable and remove it until a fixed version is available.

No confirmed safe version is listed. Consider a vendor-supported patch or temporarily restricting the affected functionality while you assess the risk.

Deactivate only when warranted by your risk profile, or when advised by your hosting provider in the limited circumstances where the vulnerability cannot otherwise be mitigated. If you’re unsure which action is appropriate, contact Fused or your hosting provider for guidance.

Technical description

The Custom Block Builder – Lazy Blocks plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 4.2.0 via multiple functions in the 'LazyBlocks_Blocks' class. This makes it possible for authenticated attackers, with Contributor-level access and above, to execute code on the server.

CVE / CNA vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Primary and upstream sources