404 to 301 – Redirect, Log and Notify 404 Errors: Cross-site request forgery
404 to 301 – Redirect, Log and Notify 404 Errors is affected by cross-site request forgery. Exposure depends on how the affected operation is made reachable by the site. Exploitation relies on a signed-in privileged user submitting an attacker-controlled request.
- Component
- 404 to 301 – Redirect, Log and Notify 404 Errors
- Plugin slug
404-to-301- Affected
- See vendor advisory
- Safe version
- See mitigation notes
- Published
- Nov 08, 2021
This CVE was published Nov 08, 2021 and is one of 3 known issues for this plugin.
Update, patch or deactivate.
Update 404 to 301 – Redirect, Log and Notify 404 Errors to a release outside the affected range, or disable and remove it until a fixed version is available.
No confirmed safe version is listed. Consider a vendor-supported patch or temporarily restricting the affected functionality while you assess the risk.
Deactivate only when warranted by your risk profile, or when advised by your hosting provider in the limited circumstances where the vulnerability cannot otherwise be mitigated. If you’re unsure which action is appropriate, contact Fused or your hosting provider for guidance.
Technical description
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
NVD vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N