Redirect 404 Error Page to Homepage or Custom Page with Logs <= 1.7.8 - Log Deletion via Cross-Site Request Forgery
Strategic Overview
- Status
- Patched in 1.7.9
- Affected Plugin
- Redirect 404 Error Page to Homepage or Custom Page with Logs
- Affected Version
<= 1.7.8- CVSS
- 4.3Medium
- Weakness type
- CWE-352 · Cross-Site Request Forgery (CSRF)
- CVE
CVE-2021-24767
At a glance
CVE-2021-24767 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the Redirect 404 Error Page to Homepage or Custom Page with Logs WordPress plugin, affecting versions <= 1.7.8. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 1.7.9; sites on affected versions should update now. Disclosed October 2021, reported by apple502j.
Vulnerability Overview
The Redirect 404 Error Page to Homepage or Custom Page with Logs WordPress plugin before 1.7.9 does not check for CSRF when deleting logs, which could allow attacker to make a logged in admin delete 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.
CWE-352: Cross-Site Request Forgery (CSRF)
Reaching this weakness in Redirect 404 Error Page to Homepage or Custom Page with Logs <= 1.7.8 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 Redirect 404 Error Page to Homepage or Custom Page with Logs the fix is 1.7.9: builds <= 1.7.8 are affected, anything from 1.7.9 onward is not.
Remediation
Update to version 1.7.9, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to Redirect 404 Error Page to Homepage or Custom Page with Logs: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Redirect 404 Error Page to Homepage or Custom Page with Logs 1.7.9 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Other vulnerabilities in Redirect 404 Error Page to Homepage or Custom Page with Logs
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C