SEO Redirection Plugin – 301 Redirect Manager <= 8.9 - Cross-Site Request Forgery
Strategic Overview
- Status
- Patched in 9.1
- Affected Plugin
- SEO Redirection Plugin – 301 Redirect Manager
- Affected Version
<= 8.9- CVSS
- 8.8High
- Weakness type
- CWE-352 · Cross-Site Request Forgery (CSRF)
- CVE
CVE-2022-38704
At a glance
CVE-2022-38704 is a high-severity Cross-Site Request Forgery (CSRF) vulnerability in the SEO Redirection Plugin WordPress plugin, affecting versions <= 8.9. It carries a CVSS score of 8.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 9.1; sites on affected versions should update now. Disclosed August 2022, reported by Muhammad Daffa.
Vulnerability Overview
The SEO Redirection Plugin – 301 Redirect Manager plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 8.9. This is due to missing nonce validation in the ~/options/option_page_404.php and ~/options/option_page_history.php files. This makes it possible for unauthenticated attackers to delete 404 redirects via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.
CWE-352: Cross-Site Request Forgery (CSRF)
Reaching this weakness in SEO Redirection Plugin <= 8.9 takes a caller who can reach the endpoint. Cross-site request forgery abuses the fact that browsers attach a victim's cookies to any request, so a state-changing action that only checks who you are, not whether you meant to act, can be triggered from another site.
An attacker who gets a logged-in user to load a crafted page can perform that action as them, with the impact scaling to whatever the victim's role is allowed to do. For SEO Redirection Plugin the fix is 9.1: builds <= 8.9 are affected, anything from 9.1 onward is not.
Remediation
Update to version 9.1, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to SEO Redirection Plugin: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: SEO Redirection Plugin 9.1 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Same weakness class
Other vulnerabilities in SEO Redirection Plugin – 301 Redirect Manager
- 8.8CVE-2021-24847: SEO Redirection <= 8.1 Subscriber+ SQL Injection
CVE-2021-24847 - 7.2CVE-2026-52702: SEO Redirection Plugin Stored XSS
CVE-2026-52702 - 6.1SEO Redirection Plugin – 301 Redirect Manager <= 7.3 Reflected XSS
- 6.1CVE-2021-24187: SEO Redirection Plugin - 301 Redirect… Reflected XSS
CVE-2021-24187 - 6.1CVE-2016-10896: SEO Redirection <= 4.2 Stored Cross-Site Scripting
CVE-2016-10896 - 6.1SEO Redirection <= 2.8 Reflected Cross-Site Scripting
- 4.8CVE-2021-24327: SEO Redirection <= 6.4 Stored Cross-Site Scripting
CVE-2021-24327 - 4.3CVE-2026-13703: SEO Redirection Plugin Information Exposure
CVE-2026-13703
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C