CVE-2025-30813
📋 TL;DR
This stored cross-site scripting (XSS) vulnerability in the Listamester WordPress plugin allows attackers to inject malicious scripts into web pages that are then executed when other users view those pages. All WordPress sites using Listamester versions up to 2.3.5 are affected. The vulnerability enables attackers to steal session cookies, redirect users, or perform actions on their behalf.
💻 Affected Systems
- Listamester 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
Attackers could steal administrator credentials, take over the WordPress site, install backdoors, deface the website, or use the compromised site to attack visitors.
Likely Case
Attackers inject malicious JavaScript to steal user session cookies, redirect users to phishing sites, or perform actions as authenticated users.
If Mitigated
With proper input validation and output encoding, malicious scripts would be neutralized before reaching users.
🎯 Exploit Status
Stored XSS vulnerabilities are commonly exploited. The Patchstack reference provides technical details about the vulnerability.
🛠️ Fix & Mitigation
✅ Official Fix
Patch Version: 2.3.6 or later
Restart Required: No
Instructions:
1. Log into WordPress admin panel. 2. Navigate to Plugins → Installed Plugins. 3. Find Listamester and click 'Update Now'. 4. Verify the plugin version is 2.3.6 or higher.
🔧 Temporary Workarounds
Disable Listamester Plugin
allTemporarily disable the vulnerable plugin until patching is possible
wp plugin deactivate listamester
Implement Content Security Policy
allAdd CSP headers to restrict script execution sources
Add to .htaccess: Header set Content-Security-Policy "default-src 'self'; script-src 'self'"
Add to nginx config: add_header Content-Security-Policy "default-src 'self'; script-src 'self'";
🧯 If You Can't Patch
- Implement web application firewall (WAF) rules to block XSS payloads
- Restrict plugin access to trusted users only and monitor for suspicious activity
🔍 How to Verify
Check if Vulnerable:
Check WordPress admin panel → Plugins → Listamester version. If version is 2.3.5 or lower, you are vulnerable.Check Version:
wp plugin get listamester --field=versionVerify Fix Applied:
After updating, verify Listamester version shows 2.3.6 or higher in WordPress plugins list.📡 Detection & Monitoring
Log Indicators:
- Unusual POST requests to Listamester endpoints containing script tags or JavaScript
- Multiple failed XSS attempts in web server logs
Network Indicators:
- Unexpected outbound connections from WordPress server after Listamester interaction
- Suspicious JavaScript payloads in HTTP requests
SIEM Query:
source="web_logs" AND ("listamester" OR "wp-content/plugins/listamester") AND ("<script" OR "javascript:" OR "onload=" OR "onerror=")