CVE-2024-35780
📋 TL;DR
This CVE describes a PHP object injection vulnerability in the Page Builder: Live Composer WordPress plugin. Attackers with contributor-level access can exploit insecure deserialization to execute arbitrary code on affected WordPress sites. All WordPress installations using vulnerable versions of this plugin are affected.
💻 Affected Systems
- Page Builder: Live Composer WordPress plugin
⚠️ Manual Verification Required
This CVE does not have specific version information in our database, so automatic vulnerability detection cannot determine if your system is affected.
Why? The CVE database entry doesn't specify which versions are vulnerable (no version ranges provided by the vendor/NVD).
🔒 Custom verification scripts are available for registered users. Sign up free to download automated test scripts.
- Review the CVE details at NVD
- Check vendor security advisories for your specific version
- Test if the vulnerability is exploitable in your environment
- Consider updating to the latest version as a precaution
⚠️ Risk & Real-World Impact
Worst Case
Remote code execution leading to complete site compromise, data theft, malware installation, or site defacement.
Likely Case
Privilege escalation from contributor to administrator, followed by site takeover and data manipulation.
If Mitigated
Limited impact if proper access controls restrict contributor accounts and input validation is enforced.
🎯 Exploit Status
Exploitation requires contributor-level access. Public proof-of-concept demonstrates the vulnerability.
🛠️ Fix & Mitigation
✅ Official Fix
Patch Version: 1.5.43 or later
Restart Required: No
Instructions:
1. Log into WordPress admin panel. 2. Navigate to Plugins > Installed Plugins. 3. Find 'Page Builder: Live Composer'. 4. Click 'Update Now' if available. 5. Alternatively, download version 1.5.43+ from WordPress repository and manually update.
🔧 Temporary Workarounds
Disable Plugin
allTemporarily deactivate the vulnerable plugin until patched.
wp plugin deactivate live-composer-page-builder
Restrict Contributor Access
allLimit contributor account creation and review existing contributor permissions.
🧯 If You Can't Patch
- Remove contributor role access entirely or implement strict review processes for contributor content.
- Implement web application firewall (WAF) rules to block deserialization attempts and monitor for suspicious activity.
🔍 How to Verify
Check if Vulnerable:
Check WordPress admin panel > Plugins > Installed Plugins for 'Page Builder: Live Composer' version 1.5.42 or earlier.Check Version:
wp plugin get live-composer-page-builder --field=versionVerify Fix Applied:
Confirm plugin version is 1.5.43 or later in WordPress admin panel.📡 Detection & Monitoring
Log Indicators:
- Unusual PHP object serialization in POST requests
- Unexpected contributor account activity
- Plugin file modification attempts
Network Indicators:
- HTTP POST requests containing serialized PHP objects to plugin endpoints
- Unusual outbound connections from WordPress server
SIEM Query:
source="wordpress.log" AND "live-composer" AND ("unserialize" OR "php_object")🔗 References
- https://patchstack.com/database/vulnerability/live-composer-page-builder/wordpress-page-builder-live-composer-plugin-1-5-42-contributor-php-object-injection-vulnerability?_s_id=cve
- https://patchstack.com/database/vulnerability/live-composer-page-builder/wordpress-page-builder-live-composer-plugin-1-5-42-contributor-php-object-injection-vulnerability?_s_id=cve
