Administrative log deletion via forged request
Published Aug 20, 2024 · Updated Aug 20, 2024
Cross-site request forgery in Pligg CMS 2.0.2 allows remote attackers to clear administrative logs through a crafted web request. The admin_log.php endpoint treats clear=1 in a POST request as authorization to erase the log without validating an anti-CSRF token. Exploitation requires an authenticated administrator to submit the forged request, after which administrative log entries are deleted.
Summary
What happened
Cross-site request forgery in Pligg CMS 2.0.2 allows remote attackers to clear administrative logs through a crafted web request. The admin_log.php endpoint treats clear=1 in a POST request as authorization to erase the log without validating an anti-CSRF token. Exploitation requires an authenticated administrator to submit the forged request, after which administrative log entries are deleted.
The record
- CVE
- CVE-2024-42606
- Published
- Aug 20, 2024
- Updated
- Aug 20, 2024
- Vendor
- Pligg
- Product
- Pligg CMS
- Classifications
- CWE-352, T1070
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 20, 2024CVE publishedPublication date reported by the CVE source.
- Aug 20, 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=2.0.2
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
- HTML CSRF proof for admin_log.phpproof 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