WP SEO Redirect 301 < 2.3.2 - Redirect Deletion via CSRF
Priority LOW 20CWE-352Published · Updated
Key facts
- Attack vector
- Network
- Privileges required
- None
- User interaction
- Required
- Attack complexity
- Low
- Impact type
- Tampering
- Confidentiality · integrity · availability
- None · Low · None
- Fix status
- Fixed
Attack profile from CVSS 3.1 · NVD. Fix status from CNA. Impact type from CWE-352.
Summary
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 it matters now
EPSS 0.0045 39th percentileScored 2026-11-07
Public exploit Yes 1 exploit referenceTagged by NVD
Fix Fixed WP SEO Redirect 301 (Unknown): 2.3.2
SSVC decision points
Not available: CISA has not published SSVC decision points for this record.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| Unknown | WP SEO Redirect 301 | 2.3.2 to before 2.3.2 | 2.3.2 | Patch available | CNA |
- WP SEO Redirect 301 VendorUnknown Affected 2.3.2 to before 2.3.2 Fixed in 2.3.2 Patch available CNA
CPE configurations NVD · 1
| CPE | Versions | Role | Vendor |
|---|---|---|---|
| cpe:2.3:a:wp_seo_redirect_301_project:wp_seo_redirect_301:*:*:*:*:*:wordpress:*:* | before 2.3.2 | Vulnerable | Wp Seo Redirect 301 Project |
- cpe:2.3:a:wp_seo_redirect_301_project:wp_seo_redirect_301:*:*:*:*:*:wordpress:*:* Versions before 2.3.2 Vulnerable ·Wp Seo Redirect 301 Project
Remediation
- Fix · CNA WP SEO Redirect 301 (Unknown) Fixed in 2.3.2
Timeline
- 2026-10-02 Threatist record created from CVE-2021-24832
- 2026-10-03 Alias added: GHSA-wmcw-73j7-m7xh
References
Sources
- CVE-2021-24832 · CVE Program
- CVE-2021-24832 · NVD
- FIRST EPSS
- GHSA-wmcw-73j7-m7xh · GitHub Advisory Database · CC BY 4.0
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences