Administrator settings modification via missing CSRF check
Published Sep 12, 2024 · Updated Sep 12, 2024
Cross-site request forgery in Blog Introduction 0.3.0 and earlier allows remote attackers to alter settings via a logged-in administrator. The options-general.php?page=Blogintroduction handler accepts posted option values, including the Websnapr API key and display settings, without a CSRF check. Exploitation requires an administrator with an active WordPress session to open attacker-controlled HTML, and the demonstrated impact is limited to plugin settings changes.
Summary
What happened
Cross-site request forgery in Blog Introduction 0.3.0 and earlier allows remote attackers to alter settings via a logged-in administrator. The options-general.php?page=Blogintroduction handler accepts posted option values, including the Websnapr API key and display settings, without a CSRF check. Exploitation requires an administrator with an active WordPress session to open attacker-controlled HTML, and the demonstrated impact is limited to plugin settings changes.
The record
- CVE
- CVE-2024-7862
- Published
- Sep 12, 2024
- Updated
- Sep 12, 2024
- Vendor
- Kim Huebel
- Product
- Blog Introduction WordPress Plugin
- Classifications
- CWE-352, CAPEC-62, T1204.002
- 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 <=0.3.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.
Weakness, pattern, technique
Public exploit references
- WPScan forged settings form 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