Lazy Blocks < 3.0.0 - Unauthenticated Remote Code Execution (CVE-2026-127048)
Lazy Blocks before 3.0.0 has a critical REST authorization flaw that can allow unauthenticated PHP code execution. Update to 3.0.0 or later.
Lazy Blocks versions before 3.0.0 are vulnerable to unauthenticated remote code execution tracked as CVE-2026-127048. The flaw affects REST authorization checks and can allow an unauthenticated requester to execute arbitrary PHP code. Update to Lazy Blocks 3.0.0 or later immediately; WordPress.org currently offers a much newer release.
Vulnerability summary
- Plugin: Custom Block Builder – Lazy Blocks
- Affected versions: Earlier than 3.0.0
- Fixed version: 3.0.0
- Current version checked: 4.5.1
- CVE: CVE-2026-127048
- Class: Unauthenticated PHP code injection leading to remote code execution
- Severity: CVSS 10.0 (Patchstack) / 9.8 Critical (WPScan)
- Required privilege: None
- User interaction: None
- Install base: 20,000+ active installations on WordPress.org
- Exploitation status: No confirmed active exploitation or CISA KEV listing was found in this run
How the RCE works
WPScan reports that affected versions do not correctly deny unauthorized requests to Lazy Blocks REST routes. The permission checks return a non-error response that WordPress interprets as authorization being granted. This can expose functionality that processes PHP-backed block output to unauthenticated callers.
Because Lazy Blocks supports custom block output written in PHP, bypassing the REST permission boundary can lead to arbitrary PHP code execution in the WordPress server context. The public proof of concept is being withheld until December 13, 2026, to give site owners time to update.
This advisory intentionally omits vulnerable route names, request bodies, and executable payloads.
Potential impact
Remote code execution is a full-site compromise condition. A successful attacker may read WordPress configuration secrets, access the database, create persistent administrator users, modify plugins or themes, plant backdoors, alter content, redirect visitors, or use the server to attack other systems.
The practical impact depends on the permissions of the PHP process and hosting isolation, but even a restricted WordPress process normally has write access to parts of wp-content and access to database credentials in wp-config.php.
Immediate mitigation
- Update Lazy Blocks to version 3.0.0 or later, preferably the current release.
- If an immediate update is impossible, deactivate Lazy Blocks until a patched version can be deployed.
- Do not rely on obscuring REST URLs; the root problem is authorization logic inside the plugin.
- Review WAF and web-server logs for unusual unauthenticated requests to WordPress REST endpoints.
- Inspect privileged users, active plugins, must-use plugins, scheduled tasks, and recently modified PHP files.
- If exploitation is suspected, preserve forensic evidence and rotate database credentials, WordPress salts, administrator passwords, and API secrets after containment.
Verify and update with WP-CLI
wp plugin get lazy-blocks --fields=name,status,version,update
wp plugin update lazy-blocks
wp plugin get lazy-blocks --fields=name,status,version,update
wp plugin verify-checksums lazy-blocks
wp cache flush
The final version must be 3.0.0 or newer. The currently available WordPress.org release is 4.5.1, so administrators should normally deploy the latest compatible release rather than stopping at the first fixed version.
Indicators and investigation
No universal malicious IP address, domain, file name, or hash has been published for CVE-2026-127048. Investigate behavioral signs of PHP execution and persistence:
- Unexpected REST requests associated with Lazy Blocks from unauthenticated clients
- New or modified PHP files under uploads, cache, plugin, theme, or must-use plugin directories
- Unrecognized administrator users or application passwords
- Unexpected plugins, themes, cron hooks, or database options
- Outbound network connections from the PHP or web-server account
- Modified core files or checksum failures
Useful defensive checks include:
wp user list --role=administrator --fields=ID,user_login,user_email,user_registered
wp plugin list --status=active --fields=name,status,version,update
wp plugin list --status=must-use --fields=name,status,version
wp cron event list --fields=hook,next_run_gmt,recurrence
wp core verify-checksums
find wp-content -type f -name '*.php' -mtime -7 -print
Compare results against a known-good deployment and backup. Check access logs, PHP error logs, process-monitoring events, WAF telemetry, and file-integrity alerts covering at least the public disclosure window.
Remediation checklist
- Update Lazy Blocks to 3.0.0 or later, preferably the latest compatible release.
- Verify plugin and WordPress core checksums.
- Review REST traffic, privileged accounts, plugins, must-use plugins, cron events, and recently modified PHP files.
- Remove unauthorized persistence only after logs and affected files have been preserved.
- Rotate credentials and invalidate sessions if code execution may have occurred.
- Test custom blocks and front-end rendering after the update and cache purge.