CVE-2025-13521
CSRF Vulnerability in WP Status Notifier Plugin Allows Settings Manipulation
Publication date: 2026-01-07
Last updated on: 2026-01-07
Assigner: Wordfence
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| wp_status_notifier | plugin | to 1.0 (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-352 | The web application does not, or cannot, sufficiently verify whether a request was intentionally provided by the user who sent the request, which could have originated from an unauthorized actor. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
The WP Status Notifier plugin for WordPress has a Cross-Site Request Forgery (CSRF) vulnerability in all versions up to and including 1.0. This occurs because the plugin does not properly validate nonces on its settings update functionality, allowing an attacker to trick a site administrator into performing unwanted actions, such as changing plugin settings, by sending a forged request.
How can this vulnerability impact me? :
This vulnerability can allow an unauthenticated attacker to modify the plugin settings by tricking an administrator into clicking a malicious link. While it does not directly compromise confidentiality or availability, it can lead to unauthorized changes in the plugin's behavior, potentially weakening site security or causing misconfigurations.
What immediate steps should I take to mitigate this vulnerability?
To mitigate this vulnerability, immediately update the WP Status Notifier plugin to a version later than 1.0 where the nonce validation issue is fixed. Additionally, avoid clicking on suspicious links and ensure that only trusted administrators have access to update plugin settings.