PatchTheCVECVE-2015-10001: The WP-Stats WordPress plugin before 2.52 does not have CSRF check when saving its settings, and did not escap
CVE-2015-10001 is a medium-severity flaw (CVSS 4.3) affecting wp-stats. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.
The WP-Stats WordPress plugin before 2.52 does not have CSRF check when saving its settings, and did not escape some of them when outputting them, allowing attacker to make logged in high privilege users change them and set Cross-Site Scripting payloads
Why this priority
- Public exploit reference
A fixed release or distro patch exists.
Risk facts
| CVSS score | 4.3 (Medium) |
| Attack vector | Network (remote) |
| Attack complexity | Low |
| Privileges needed | None |
| User interaction | Required |
| EPSS exploit chance | 0.5% (top 57%) |
| CISA exploited list | No |
| Weakness | CWE-352 |
| Published | 2021-11-01 |
| Last modified | 2026-06-17 |
Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score
Am I affected?
Timeline
- Published CVE record published
- Updated Record last modified
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.
Quick answers
How do I fix CVE-2015-10001?
wp-stats: upgrade to 2.52. Exact commands for each OS are on this page.
Is CVE-2015-10001 being exploited?
CVE-2015-10001 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.
What does CVE-2015-10001 affect?
CVE-2015-10001 affects wp-stats. Severity is medium (CVSS 4.3). The WP-Stats WordPress plugin before 2.52 does not have CSRF check when saving its settings, and did not escape some of them when outputting them, allowing attacker to make logged in high privilege users change them and set Cross-Site Scrip
How urgent is CVE-2015-10001?
Priority 31/100. Public exploit reference