CVE-2025-32613
📋 TL;DR
This stored cross-site scripting (XSS) vulnerability in the WordPress Debug Log Manager plugin allows attackers to inject malicious scripts that execute when other users view affected pages. All WordPress sites using vulnerable versions of this plugin are affected, potentially compromising user sessions and site security.
💻 Affected Systems
- WordPress Debug Log Manager 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
Attackers could steal administrator credentials, take over the WordPress site, install backdoors, deface the site, or pivot to attack visitors' browsers.
Likely Case
Session hijacking, cookie theft, credential harvesting, or redirection to malicious sites for users with access to the debug log interface.
If Mitigated
Limited to authenticated users only, with minimal impact if proper content security policies and input validation are in place.
🎯 Exploit Status
Stored XSS vulnerabilities in WordPress plugins are commonly exploited. Attackers need some level of access to inject payloads, but once stored, they affect all users viewing the compromised page.
🛠️ Fix & Mitigation
✅ Official Fix
Patch Version: 2.3.5 or later
Restart Required: No
Instructions:
1. Log into WordPress admin panel. 2. Navigate to Plugins → Installed Plugins. 3. Find 'Debug Log Manager' and click 'Update Now'. 4. Alternatively, download version 2.3.5+ from WordPress.org and manually replace the plugin files.
🔧 Temporary Workarounds
Disable Debug Log Manager Plugin
allTemporarily deactivate the vulnerable plugin until patched
wp plugin deactivate debug-log-manager
Implement Content Security Policy
allAdd CSP headers to restrict script execution
Add to .htaccess: Header set Content-Security-Policy "default-src 'self'; script-src 'self'"
Or add to wp-config.php: header("Content-Security-Policy: default-src 'self'; script-src 'self'");
🧯 If You Can't Patch
- Restrict plugin access to trusted administrators only
- Implement web application firewall rules to block XSS payloads
🔍 How to Verify
Check if Vulnerable:
Check WordPress admin → Plugins → Debug Log Manager → Version. If version is 2.3.4 or lower, you are vulnerable.Check Version:
wp plugin get debug-log-manager --field=versionVerify Fix Applied:
After updating, verify the plugin version shows 2.3.5 or higher in WordPress admin panel.📡 Detection & Monitoring
Log Indicators:
- Unusual POST requests to debug-log-manager admin endpoints
- JavaScript payloads in request parameters
- Multiple failed login attempts followed by plugin access
Network Indicators:
- Suspicious script tags in HTTP requests to /wp-admin/admin.php?page=debug-log-manager
- Unexpected redirects from debug log pages
SIEM Query:
source="*access.log*" AND (uri_path="*debug-log-manager*" AND (method="POST" OR params="*<script>*"))