CVE-2025-22572
📋 TL;DR
This stored cross-site scripting (XSS) vulnerability in the Legacy ePlayer WordPress plugin allows attackers to inject malicious scripts into web pages. When users view pages containing the injected scripts, the attacker can steal session cookies, redirect users, or perform actions on their behalf. All WordPress sites using Legacy ePlayer versions up to 0.9.9 are affected.
💻 Affected Systems
- Legacy ePlayer 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 session cookies, take over WordPress sites, install backdoors, deface websites, or redirect visitors to malicious sites.
Likely Case
Attackers inject malicious JavaScript to steal user session cookies, potentially compromising user accounts and performing unauthorized actions.
If Mitigated
With proper input validation and output encoding, malicious scripts would be neutralized before reaching users, preventing exploitation.
🎯 Exploit Status
Stored XSS vulnerabilities are commonly exploited, though specific exploit details for this CVE aren't publicly documented.
🛠️ Fix & Mitigation
✅ Official Fix
Patch Version: 0.9.10 or later
Restart Required: No
Instructions:
1. Log into WordPress admin panel. 2. Navigate to Plugins > Installed Plugins. 3. Find Legacy ePlayer and click 'Update Now'. 4. Verify update to version 0.9.10 or later.
🔧 Temporary Workarounds
Disable Legacy ePlayer plugin
allTemporarily deactivate the vulnerable plugin until patched
wp plugin deactivate legacy-eplayer
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
- Disable the Legacy ePlayer plugin immediately
- Implement web application firewall (WAF) rules to block XSS payloads
🔍 How to Verify
Check if Vulnerable:
Check WordPress admin panel > Plugins > Installed Plugins for Legacy ePlayer versionCheck Version:
wp plugin get legacy-eplayer --field=versionVerify Fix Applied:
Verify Legacy ePlayer plugin version is 0.9.10 or higher in WordPress admin📡 Detection & Monitoring
Log Indicators:
- Unusual POST requests to Legacy ePlayer endpoints
- Suspicious JavaScript payloads in request parameters
Network Indicators:
- Malicious script tags in HTTP requests to WordPress admin or plugin endpoints
SIEM Query:
source="wordpress.log" AND ("legacy-eplayer" OR "eplayer") AND ("script" OR "javascript" OR "onload" OR "onerror")