CVE-2025-23980
📋 TL;DR
This CSRF vulnerability in the WordPress Full Circle plugin allows attackers to trick authenticated administrators into performing unintended actions, which can lead to stored cross-site scripting (XSS). Attackers can inject malicious scripts that execute in users' browsers when they visit affected pages. All WordPress sites using Full Circle plugin versions up to 0.5.7.8 are affected.
💻 Affected Systems
- WordPress Full Circle 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, deface websites, redirect users to malicious sites, or perform actions on behalf of authenticated users.
Likely Case
Attackers create fake forms or links that trick administrators into unknowingly submitting malicious content, leading to stored XSS payloads that affect site visitors.
If Mitigated
With proper CSRF tokens and input validation, the attack chain is broken and no malicious actions can be performed.
🎯 Exploit Status
Exploitation requires social engineering to trick authenticated users into clicking malicious links or visiting crafted pages.
🛠️ Fix & Mitigation
✅ Official Fix
Patch Version: Version after 0.5.7.8
Restart Required: No
Instructions:
1. Log into WordPress admin panel. 2. Navigate to Plugins → Installed Plugins. 3. Find Full Circle plugin. 4. Click 'Update Now' if update available. 5. If no update available, deactivate and remove plugin.
🔧 Temporary Workarounds
Implement CSRF Protection
allAdd CSRF tokens to all form submissions and state-changing actions in the plugin
Input Validation and Sanitization
allImplement strict input validation and output encoding for all user-controllable data
🧯 If You Can't Patch
- Deactivate and remove the Full Circle plugin from WordPress
- Implement web application firewall (WAF) rules to block CSRF attempts and XSS payloads
🔍 How to Verify
Check if Vulnerable:
Check WordPress admin → Plugins → Installed Plugins → Full Circle version. If version is 0.5.7.8 or earlier, you are vulnerable.Check Version:
wp plugin list --name=full-circle --field=versionVerify Fix Applied:
After updating, verify Full Circle plugin version is higher than 0.5.7.8 in WordPress admin panel.📡 Detection & Monitoring
Log Indicators:
- Unusual POST requests to Full Circle plugin endpoints without proper referrer headers
- Multiple failed CSRF token validations
- Unexpected content modifications in database
Network Indicators:
- Requests with suspicious parameters containing script tags or JavaScript code
- Cross-origin requests to Full Circle endpoints
SIEM Query:
source="wordpress.log" AND ("full-circle" OR "wp-content/plugins/full-circle") AND (POST OR "csrf" OR "referer")