Logging disablement via unchecked settings request
Published Jun 21, 2024 · Updated Aug 1, 2024
CSRF in WP Logs Book 1.0.1 and earlier allows remote attackers to disable activity logging through a forged settings request. The wp-admin settings endpoint accepts wplb_error_404_log and wplb_login_attack_log POST values without a CSRF token check. A logged-in administrator must open attacker-controlled HTML; the resulting request can disable failed-login and 404-error logging.
Summary
What happened
CSRF in WP Logs Book 1.0.1 and earlier allows remote attackers to disable activity logging through a forged settings request. The wp-admin settings endpoint accepts wplb_error_404_log and wplb_login_attack_log POST values without a CSRF token check. A logged-in administrator must open attacker-controlled HTML; the resulting request can disable failed-login and 404-error logging.
The record
- CVE
- CVE-2024-4474
- Published
- Jun 21, 2024
- Updated
- Aug 1, 2024
- Vendor
- oneTarek
- Product
- WP Logs Book
- Classifications
- CWE-352, T1562.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 21, 2024CVE publishedPublication date reported by the CVE source.
- Aug 1, 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=0 <=1.0.1
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.
Weakness, pattern, technique
Public exploit references
- WPScan forged settings-request 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