PatchTheCVECVE-2022-1709: The Throws SPAM Away WordPress plugin before 3.3.1 does not have CSRF checks in place when deleting comments (
CVE-2022-1709 is a medium-severity flaw (CVSS 4.3) affecting throws spam away. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.
The Throws SPAM Away WordPress plugin before 3.3.1 does not have CSRF checks in place when deleting comments (either all, spam, or pending), allowing attackers to make a logged in admin delete comments via a CSRF attack
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.4% (top 62%) |
| CISA exploited list | No |
| Weakness | CWE-352 |
| Published | 2022-06-08 |
| 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-2022-1709?
throws spam away: upgrade to 3.3.1. Exact commands for each OS are on this page.
Is CVE-2022-1709 being exploited?
CVE-2022-1709 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-2022-1709 affect?
CVE-2022-1709 affects throws spam away. Severity is medium (CVSS 4.3). The Throws SPAM Away WordPress plugin before 3.3.1 does not have CSRF checks in place when deleting comments (either all, spam, or pending), allowing attackers to make a logged in admin delete comments via a CSRF attack
How urgent is CVE-2022-1709?
Priority 29/100. Public exploit reference