Log deletion via missing bulk-action nonce
Published Nov 8, 2021 · Updated Aug 3, 2024
CSRF in 404 to 301 before 3.0.9 allows remote attackers to make a logged-in administrator delete every recorded 404 log entry. The bulk_clean action on the plugin's logs administration page accepts a state-changing GET request without verifying a CSRF nonce. Exploitation requires an authenticated administrator to visit the crafted URL, and the resulting action erases the plugin's entire 404 history.
Summary
What happened
CSRF in 404 to 301 before 3.0.9 allows remote attackers to make a logged-in administrator delete every recorded 404 log entry. The bulk_clean action on the plugin's logs administration page accepts a state-changing GET request without verifying a CSRF nonce. Exploitation requires an authenticated administrator to visit the crafted URL, and the resulting action erases the plugin's entire 404 history.
The record
- CVE
- CVE-2021-24766
- Published
- Nov 8, 2021
- Updated
- Aug 3, 2024
- Vendor
- joelcj91
- Product
- 404 to 301 – Redirect, Log and Notify 404 Errors
- Classifications
- CWE-352, T1485
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Nov 8, 2021CVE publishedPublication date reported by the CVE source.
- Aug 3, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=3.0.9 <3.0.9
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
- WPScan bulk_clean CSRF proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo