PatchTheCVECVE-2021-24832: The WP SEO Redirect 301 WordPress plugin before 2.3.2 does not have CSRF in place when deleting redirects, whi
CVE-2021-24832 is a medium-severity flaw (CVSS 4.3) affecting wp seo redirect 301. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.
The WP SEO Redirect 301 WordPress plugin before 2.3.2 does not have CSRF in place when deleting redirects, which could allow attackers to make a logged in admin delete them 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 61%) |
| CISA exploited list | No |
| Weakness | CWE-352 |
| Published | 2021-11-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-2021-24832?
wp seo redirect 301: upgrade to 2.3.2. Exact commands for each OS are on this page.
Is CVE-2021-24832 being exploited?
CVE-2021-24832 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-24832 affect?
CVE-2021-24832 affects wp seo redirect 301. Severity is medium (CVSS 4.3). The WP SEO Redirect 301 WordPress plugin before 2.3.2 does not have CSRF in place when deleting redirects, which could allow attackers to make a logged in admin delete them via a CSRF attack
How urgent is CVE-2021-24832?
Priority 30/100. Public exploit reference