404 to 301 <= 3.0.8 - Logs Deletion via Cross-Site Request Forgery
Strategic Overview
- Status
- Patched in 3.0.9
- Affected Version
< 3.0.9- CVSS
- 6.5Medium
- Weakness type
- CWE-352 · Cross-Site Request Forgery (CSRF)
- CVE
CVE-2021-24766
At a glance
CVE-2021-24766 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the 404 to 301 WordPress plugin, affecting versions < 3.0.9. It carries a CVSS score of 6.5 (reachable over the network; low attack complexity; high integrity impact). Exploitation requires no authentication. The issue is fixed in version 3.0.9; sites on affected versions should update now. Disclosed October 2021, reported by apple502j.
Vulnerability Overview
The 404 to 301 – Redirect, Log and Notify 404 Errors WordPress plugin before 3.0.9 does not have CSRF check in place when cleaning the logs, which could allow attacker to make a logged in admin delete all of them via a CSRF attack
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 integrity.
CWE-352: Cross-Site Request Forgery (CSRF)
Reaching this weakness in 404 to 301 < 3.0.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 404 to 301 the fix is 3.0.9: builds < 3.0.9 are affected, anything from 3.0.9 onward is not.
Remediation
Update to version 3.0.9, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to 404 to 301: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: 404 to 301 3.0.9 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Other vulnerabilities in 404 to 301 – Redirect Manager, 301 Redirection, 404 Error Logs & 404 Monitoring
- 9.8CVE-2015-9323: 404 to 301 SQL Injection
CVE-2015-9323 - 8.8Freemius SDK <= 2.2.3 Arbitrary Options Update
- 7.2404 to 301 <= 2.3.0 Stored Cross-Site Scripting
- 6.4CVE-2021-4338: 404 to 301 <= 3.0.7 Redirect Creation
CVE-2021-4338 - 6.1CVE-2023-33999: Freemius SDK <= 2.5.9 Reflected Cross-Site Scripting
CVE-2023-33999 - 6.1404 to 301 – Redirect, Log and Notify 404 Errors Reflected XSS
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C