Custom Block Builder – Lazy Blocks vulnerabilities
Plugin slug lazy-blocks · 4 known vulnerabilities · latest disclosed 2026-06-11 · WordPress.org page
Every listed vulnerability has a fix. Version 4.3.0 or later is not affected by any of them. If your site runs an older version, update it.
1 of 4 rated high or critical (CVSS 7 or more).
Known vulnerabilities in Custom Block Builder – Lazy Blocks
| Severity | Affected versions | Fixed in | CVE | Published | Details |
|---|---|---|---|---|---|
| Medium 4.4 | < 4.3.0 | 4.3.0 | CVE-2026-8981 | 2026-06-11 | Advisory |
| High 8.8 | <= 4.2.0 | 4.2.1 | CVE-2026-1560 | 2026-02-10 | Advisory |
| Medium 4.3 | <= 4.1.0 | 4.1.1 | CVE-2025-58258 | 2025-09-22 | Advisory |
| Medium 6.1 | <= 3.8.2 | 3.8.3 | CVE-2024-12878 | 2025-02-04 | Advisory |
Check if a site is affected
Enter a site address to see which version of Custom Block Builder – Lazy Blocks and other plugins it runs, and whether they match a known vulnerability.
Questions
Is the Custom Block Builder – Lazy Blocks plugin safe to use?
All 4 known issues are fixed in current versions (4.3.0 or later). Keeping it updated is what matters.
How do I check which version of Custom Block Builder – Lazy Blocks my site runs?
In WordPress go to Plugins > Installed Plugins. From the outside, the free PluginPeek scan below reads the version from the site's public files.
How do I fix a vulnerable plugin?
Make a full backup, then update it from Dashboard > Updates and check the site afterwards. If you would rather not, we can do it for a fixed $99, paid after you have checked the site.