Custom Block Builder – Lazy Blocks
lazy-blocks · plugin
Known security vulnerabilities for Custom Block Builder – Lazy Blocks. Find out in seconds which version runs on your site with WP Lens.
5 known vulnerabilities
1 critical · 1 exploitable without logging in · 2 with public exploit code · latest Nov 15, 2026
Before you install
Use with care
- 1 record needing no login published in the last two years.
If you install it, keep auto-updates on and monitor the site: when a new record appears you need to update quickly.
This assessment relies only on published vulnerability records and wordpress.org data; it does not review the code.
Is this component installed on your sites, and in which version? See it from inside the site with Noroxi Connector
Listed on wordpress.org · latest 4.5.2 · last updated Nov 17, 2026 · 20K+ installs
wordpress.org status checked on Nov 19, 2026
Vulnerabilities
- Critical 9.8
CVE-2026-127048unauthenticated→ 3.0.0
Lazy Blocks < 3.0.0 - Unauthenticated RCE
- High 8.8
CVE-2026-1560contributor+≤ 4.2.0
Custom Block Builder – Lazy Blocks <= 4.2.0 - Authenticated (Contributor+) Remote Code Execution
- High 7.1
CVE-2024-12878admin→ 3.8.3
Custom Block Builder – Lazy Blocks < 3.8.3 - Reflected XSS
- Medium 4.3
CVE-2025-58258login required≤ 4.1.0
WordPress Lazy Blocks Plugin <= 4.1.0 - Broken Access Control Vulnerability
- Low 3.5
CVE-2026-8981admin→ 4.3.0
Lazy Blocks < 4.3.0 - Admin+ Stored XSS via Custom Block Frontend HTML
The access label is read from the record's own text (e.g. “subscriber+”: subscriber and above). When the text names no role, CVSS decides between “login required” and “high privilege”; no role name is invented. “Needs a click”: the attack depends on a logged-in user following a link (CSRF, reflected XSS).
Exploited this week · every Monday
New KEV entries, fresh PoCs, WordPress triage and what to do this week. No account needed.