Settings modification via missing CSRF validation
Published Sep 12, 2024 · Updated Sep 12, 2024
Cross-site request forgery in Elliot ILC Thickbox 1.0 and earlier allows remote attackers to change plugin settings via a forged request. The admin settings handler accepts the ilc_thickbox_css POST field and updates configuration without validating a CSRF nonce. Exploitation requires a logged-in administrator to open attacker-controlled HTML, after which the browser submits the settings form with the administrator's session.
Summary
What happened
Cross-site request forgery in Elliot ILC Thickbox 1.0 and earlier allows remote attackers to change plugin settings via a forged request. The admin settings handler accepts the ilc_thickbox_css POST field and updates configuration without validating a CSRF nonce. Exploitation requires a logged-in administrator to open attacker-controlled HTML, after which the browser submits the settings form with the administrator's session.
The record
- CVE
- CVE-2024-7820
- Published
- Sep 12, 2024
- Updated
- Sep 12, 2024
- Vendor
- Elliot
- Product
- ILC Thickbox
- Classifications
- CWE-352, T1204.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 12, 2024CVE publishedPublication date reported by the CVE source.
- Sep 12, 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
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 CSRF settings-update proof of conceptproof of concept · validated
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