CVE-2025-31093
📋 TL;DR
This vulnerability allows attackers to inject malicious scripts into web pages generated by the RPS Include Content WordPress plugin, which are then executed in users' browsers. It affects all WordPress sites using the plugin version 1.2.1 or earlier. Attackers can steal session cookies, redirect users to malicious sites, or perform actions on behalf of authenticated users.
💻 Affected Systems
- RPS Include Content 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
Complete account takeover, data theft, and full site compromise if admin sessions are hijacked.
Likely Case
Session hijacking of regular users, defacement of site content, and credential theft.
If Mitigated
Limited impact with proper Content Security Policy (CSP) headers and input validation in place.
🎯 Exploit Status
DOM-based XSS typically requires user interaction but can be exploited via crafted links or embedded content.
🛠️ Fix & Mitigation
✅ Official Fix
Patch Version: 1.2.2 or later
Restart Required: No
Instructions:
1. Log into WordPress admin panel. 2. Navigate to Plugins > Installed Plugins. 3. Find 'RPS Include Content' and click 'Update Now'. 4. Verify plugin version is 1.2.2 or higher.
🔧 Temporary Workarounds
Disable Plugin
allTemporarily disable the vulnerable plugin until patched.
wp plugin deactivate rps-include-content
Implement CSP Headers
allAdd Content Security Policy headers to mitigate XSS impact.
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
- Remove the RPS Include Content plugin entirely from your WordPress installation.
- Implement a Web Application Firewall (WAF) with XSS protection rules.
🔍 How to Verify
Check if Vulnerable:
Check WordPress admin panel > Plugins > Installed Plugins for RPS Include Content version 1.2.1 or lower.Check Version:
wp plugin get rps-include-content --field=versionVerify Fix Applied:
Verify plugin version shows 1.2.2 or higher in WordPress admin panel.📡 Detection & Monitoring
Log Indicators:
- Unusual POST/GET requests containing script tags or JavaScript code to plugin endpoints.
- Multiple failed login attempts following suspicious page visits.
Network Indicators:
- HTTP requests with suspicious parameters like <script> tags or JavaScript events.
- Outbound connections to unknown domains after visiting specific pages.
SIEM Query:
source="wordpress.log" AND ("rps-include-content" OR "RPS Include Content") AND ("<script>" OR "javascript:" OR "onload=" OR "onerror=")