CVE-2025-58859
📋 TL;DR
A Cross-Site Request Forgery (CSRF) vulnerability in the WordPress Add to Feedly plugin allows attackers to trick authenticated administrators into performing unintended actions, which can lead to stored cross-site scripting (XSS) attacks. This affects all WordPress sites using the Add to Feedly plugin versions up to 1.2.11. The vulnerability enables attackers to inject malicious scripts that execute in victims' browsers.
💻 Affected Systems
- WordPress Add to Feedly 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 inject persistent malicious scripts that steal administrator credentials, hijack sessions, deface websites, or redirect visitors to malicious sites, potentially compromising the entire WordPress installation.
Likely Case
Attackers create fake admin interfaces or forms that trick logged-in administrators into executing actions that inject malicious JavaScript, leading to session hijacking or credential theft.
If Mitigated
With proper CSRF protections and content security policies, the attack surface is reduced, but the vulnerability still exists in the plugin code.
🎯 Exploit Status
Exploitation requires tricking an authenticated administrator into clicking a malicious link or visiting a crafted page. CSRF attacks are well-understood and relatively easy to weaponize.
🛠️ Fix & Mitigation
✅ Official Fix
Patch Version: 1.2.12 or later
Restart Required: No
Instructions:
1. Log into WordPress admin panel. 2. Navigate to Plugins > Installed Plugins. 3. Find 'Add to Feedly' and click 'Update Now' if available. 4. Alternatively, download version 1.2.12+ from WordPress.org and manually update via FTP or file manager.
🔧 Temporary Workarounds
Disable Add to Feedly plugin
allTemporarily deactivate the vulnerable plugin until patched
wp plugin deactivate add-to-feedly
Implement CSRF protection headers
allAdd Content Security Policy headers to limit script execution
Add to .htaccess: Header set Content-Security-Policy "script-src 'self'"
Add to nginx config: add_header Content-Security-Policy "script-src 'self'";
🧯 If You Can't Patch
- Remove the Add to Feedly plugin entirely from your WordPress installation
- Implement strict access controls and monitor administrator account activity for suspicious behavior
🔍 How to Verify
Check if Vulnerable:
Check WordPress admin panel > Plugins > Installed Plugins for 'Add to Feedly' version. If version is 1.2.11 or earlier, you are vulnerable.Check Version:
wp plugin get add-to-feedly --field=versionVerify Fix Applied:
After updating, verify the plugin version shows 1.2.12 or later in WordPress admin panel.📡 Detection & Monitoring
Log Indicators:
- Unusual POST requests to WordPress admin-ajax.php or admin-post.php endpoints
- Multiple failed CSRF token validation attempts in WordPress debug logs
- Unexpected plugin activation/deactivation events
Network Indicators:
- HTTP requests with missing or invalid nonce parameters in WordPress admin URLs
- Cross-origin requests to WordPress admin endpoints from unexpected domains
SIEM Query:
source="wordpress.log" AND ("admin-ajax.php" OR "admin-post.php") AND ("action=add_to_feedly" OR "plugin=add-to-feedly")