PatchTheCVECVE-2021-25073: The WP125 WordPress plugin before 1.5.5 does not have CSRF checks in various action, for example when deleting
CVE-2021-25073 is a high-severity flaw (CVSS 8.8) affecting wp125. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.
The WP125 WordPress plugin before 1.5.5 does not have CSRF checks in various action, for example when deleting an ad, allowing attackers to make a logged in admin delete them via a CSRF attack
Why this priority
- High severity
- Public exploit reference
A fixed release or distro patch exists.
Risk facts
| CVSS score | 8.8 (High) |
| Attack vector | Network (remote) |
| Attack complexity | Low |
| Privileges needed | None |
| User interaction | Required |
| EPSS exploit chance | 0.7% (top 47%) |
| CISA exploited list | No |
| Weakness | CWE-352 |
| Published | 2022-01-24 |
| 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-2021-25073?
wp125: upgrade to 1.5.5. Exact commands for each OS are on this page.
Is CVE-2021-25073 being exploited?
CVE-2021-25073 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-2021-25073 affect?
CVE-2021-25073 affects wp125. Severity is high (CVSS 8.8). The WP125 WordPress plugin before 1.5.5 does not have CSRF checks in various action, for example when deleting an ad, allowing attackers to make a logged in admin delete them via a CSRF attack
How urgent is CVE-2021-25073?
Priority 49/100. High severity; Public exploit reference