CVE-2025-13521
CVSS 4.3 MediumEPSS 0.0%
- CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N
- Published: 2026-01-07T12:16:48.770
The WP Status Notifier plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 1.0. This is due to missing or incorrect nonce validation on the settings update functionality. This makes it possible for unauthenticated attackers to update the plugin settings via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.
Related CVE by CWE
No related CWE found.
Top CVE for Vendor
No vendor taxonomy on this entry.
Recently Exploited Similar Vulnerabilities
No recent KEV-listed items for this vendor/product.
How to fix CVE-2025-13521
CVE-2025-13521 is a medium severity vulnerability affecting the affected product.
Description: The WP Status Notifier plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 1.0. This is due to missing or incorrect nonce validation on the settings update functionality. This makes it possible for unauthenticated attackers to update the plugin settings via a forged request granted they can trick […]
Affected Versions:
❌ Vulnerable: ≤ 1.0
✅ Safe: ≥ 1.1
Exploit Difficulty: MEDIUM
⏱️ Time to exploit: 1-4 hours
🛠️ Required skills: Intermediate security knowledge
💰 Public exploits: May be available
How to Fix:
- Check if you're running the affected product
- Verify version (vulnerable: ≤ 1.0)
- Update to ≥ 1.1 or later
- If patching is not immediately possible: restrict network exposure, apply least-privilege access
- Test the fix in a staging environment first
- Review logs for signs of exploitation
- Monitor for IOCs (Indicators of Compromise)
- Enable automatic security updates
- Set up vulnerability monitoring
- Review and harden security configurations
Description: The WP Status Notifier plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 1.0. This is due to missing or incorrect nonce validation on the settings update functionality. This makes it possible for unauthenticated attackers to update the plugin settings via a forged request granted they can trick […]
Affected Versions:
❌ Vulnerable: ≤ 1.0
✅ Safe: ≥ 1.1
Exploit Difficulty: MEDIUM
⏱️ Time to exploit: 1-4 hours
🛠️ Required skills: Intermediate security knowledge
💰 Public exploits: May be available
How to Fix:
1 Identify affected systems
- Check if you're running the affected product
- Verify version (vulnerable: ≤ 1.0)
2 Immediate actions
- Update to ≥ 1.1 or later
- If patching is not immediately possible: restrict network exposure, apply least-privilege access
3 Verification
- Test the fix in a staging environment first
- Review logs for signs of exploitation
- Monitor for IOCs (Indicators of Compromise)
4 Long-term prevention
- Enable automatic security updates
- Set up vulnerability monitoring
- Review and harden security configurations
Exploit Difficulty Assessment
MEDIUM
Time to Exploit: 1-4 hours
Skills Required: Intermediate security knowledge
Public Exploits: May be available
Affected Versions
Vulnerable: ≤ 1.0
Safe: ≥ 1.1
Vulnerability Timeline
Jan 07, 2026
Vulnerability Published
CVE details first published to NVD database
Jan 07, 2026
Imported to Database
Added to this CVE tracking system
Detection Rules & IOCs
No specific detection rules generated for this vulnerability type.
No vendor/product data available.