Loading vulnerability…
The Custom Block Builder – Lazy Blocks plugin for WordPress is vulnerable to remote code execution (RCE) in all versions up to and including 4.2.0. The issue is reachable via multiple functions in the LazyBlocks_Blocks class, allowing an authenticated attacker with Contributor-level privileges (or higher) to execute arbitrary code on the server.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
Repository contains a minimal proof-of-concept exploit for CVE-2026-1560 affecting the WordPress plugin “Custom Block Builder – Lazy Blocks” <= 4.2.0. Structure: (1) README.md documents the vulnerability, affected versions, and the vulnerable REST route; it explains the root cause as a weak permission check on the block preview REST API combined with an eval-based PHP rendering sink (php_eval) that executes attacker-controlled code. (2) poc.py is a Python 3 script using `requests` to perform an authenticated POST to `/wp-json/lazy-blocks/v1/block-builder-preview/` with a crafted JSON `block` object setting `code_output_method` to `php` and injecting PHP into `code_editor_html`. The injected PHP calls `system(COMMAND)` and prints a marker string (RCE_OK) to confirm successful code execution. The exploit’s capability is authenticated RCE (OS command execution) requiring valid credentials with `edit_posts` capability and a REST authentication method compatible with Basic Auth (as implemented in the PoC).
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
6 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.