CVE-2025-30770
📋 TL;DR
This DOM-based Cross-Site Scripting (XSS) vulnerability in the Charitable WordPress plugin allows attackers to inject malicious scripts into web pages viewed by other users. It affects all Charitable plugin installations from unspecified versions through 1.8.4.7. Attackers can execute arbitrary JavaScript in victims' browsers when they visit compromised pages.
💻 Affected Systems
- WordPress Charitable 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 session cookies, perform actions as authenticated users, redirect to malicious sites, or install malware on visitors' systems.
Likely Case
Session hijacking, credential theft, defacement of donation pages, or redirection to phishing sites.
If Mitigated
Limited impact if Content Security Policy (CSP) headers are properly configured and input validation is enforced elsewhere.
🎯 Exploit Status
DOM-based XSS typically requires user interaction but can be exploited via crafted links or forms.
🛠️ Fix & Mitigation
✅ Official Fix
Patch Version: Versions after 1.8.4.7
Vendor Advisory: https://patchstack.com/database/wordpress/plugin/charitable/vulnerability/wordpress-charitable-1-8-4-7-cross-site-scripting-xss-vulnerability?_s_id=cve
Restart Required: No
Instructions:
1. Log into WordPress admin panel. 2. Navigate to Plugins > Installed Plugins. 3. Find Charitable plugin. 4. Click 'Update Now' if available. 5. Alternatively, download latest version from WordPress.org and manually update.
🔧 Temporary Workarounds
Disable Charitable plugin
allTemporarily disable the vulnerable plugin until patched.
wp plugin deactivate charitable
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 using authentication
🔍 How to Verify
Check if Vulnerable:
Check WordPress admin > Plugins > Installed Plugins for Charitable version. If version is 1.8.4.7 or earlier, you are vulnerable.Check Version:
wp plugin get charitable --field=versionVerify Fix Applied:
Verify Charitable plugin version is higher than 1.8.4.7 in WordPress admin panel.📡 Detection & Monitoring
Log Indicators:
- Unusual POST/GET requests with script tags or JavaScript payloads to Charitable plugin endpoints
- Multiple failed XSS attempts in web server logs
Network Indicators:
- HTTP requests containing suspicious script tags or JavaScript in parameters
- Unusual outbound connections from WordPress site after visiting donation pages
SIEM Query:
source="web_logs" AND (uri_path="/wp-content/plugins/charitable" OR user_agent CONTAINS "<script")