CVE-2025-13537
📋 TL;DR
The Live Composer WordPress plugin has stored XSS vulnerabilities allowing authenticated attackers with Contributor access or higher to inject malicious scripts via DOM manipulation. These scripts execute when users view compromised pages, potentially compromising visitor sessions and site integrity. All WordPress sites using Live Composer versions up to 2.0.2 are affected.
💻 Affected Systems
- Live Composer – Free WordPress Website Builder
⚠️ 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
Attackers could steal administrator credentials, deface websites, redirect visitors to malicious sites, or install backdoors for persistent access.
Likely Case
Attackers with contributor accounts inject malicious scripts to steal user session cookies, perform phishing attacks, or modify page content.
If Mitigated
With proper input validation and output escaping, script injection would fail, preventing execution of malicious payloads.
🎯 Exploit Status
Exploitation requires authenticated access but is technically simple once access is obtained. The vulnerability is in client-side JavaScript DOM manipulation.
🛠️ Fix & Mitigation
✅ Official Fix
Patch Version: 2.0.3 or later
Vendor Advisory: https://plugins.trac.wordpress.org/changeset/3419715/
Restart Required: No
Instructions:
1. Log into WordPress admin panel. 2. Navigate to Plugins → Installed Plugins. 3. Find Live Composer plugin. 4. Click 'Update Now' if update available. 5. If no update appears, manually download version 2.0.3+ from WordPress.org and replace plugin files.
🔧 Temporary Workarounds
Disable Live Composer Plugin
allTemporarily disable the vulnerable plugin until patched
wp plugin deactivate live-composer-page-builder
Restrict Contributor Access
allTemporarily remove contributor-level user accounts or restrict their capabilities
🧯 If You Can't Patch
- Implement Content Security Policy (CSP) headers to restrict script execution
- Use web application firewall (WAF) rules to detect and block XSS payloads
🔍 How to Verify
Check if Vulnerable:
Check WordPress admin panel → Plugins → Live Composer version. If version is 2.0.2 or lower, you are vulnerable.Check Version:
wp plugin get live-composer-page-builder --field=versionVerify Fix Applied:
After updating, verify plugin version shows 2.0.3 or higher in WordPress admin panel.📡 Detection & Monitoring
Log Indicators:
- Unusual POST requests to WordPress admin-ajax.php with script payloads
- Multiple page edits from contributor accounts in short time
Network Indicators:
- Inbound requests containing JavaScript in POST parameters to WordPress endpoints
SIEM Query:
source="wordpress.log" AND ("live-composer" OR "admin-ajax.php") AND ("script" OR "onload" OR "javascript:")🔗 References
- https://plugins.trac.wordpress.org/browser/live-composer-page-builder/trunk/js/src/client/frontend/index.js#L126
- https://plugins.trac.wordpress.org/browser/live-composer-page-builder/trunk/js/src/client/frontend/index.js#L926
- https://plugins.trac.wordpress.org/changeset/3419715/
- https://www.wordfence.com/threat-intel/vulnerabilities/id/a9f8ab73-8c2a-4551-bad9-4e5cc67231e5?source=cve
