Forged revision reports via missing edit-token check
Published Jan 25, 2021 · Updated Aug 3, 2024
Cross-site request forgery in Kenny2github Report before f828dc6 allows remote attackers to submit revision reports through a user's session. SpecialReport.php accepted posted reason and revision values in onPost() and inserted a database record without validating a MediaWiki edit token. Exploitation requires a registered user to interact with attacker-controlled content while signed in; the consequence is an unauthorized revision report.
Summary
What happened
Cross-site request forgery in Kenny2github Report before f828dc6 allows remote attackers to submit revision reports through a user's session. SpecialReport.php accepted posted reason and revision values in onPost() and inserted a database record without validating a MediaWiki edit token. Exploitation requires a registered user to interact with attacker-controlled content while signed in; the consequence is an unauthorized revision report.
The record
- CVE
- CVE-2021-21275
- Published
- Jan 25, 2021
- Updated
- Aug 3, 2024
- Vendor
- Kenny2github
- Product
- Report
- Classifications
- CWE-352, CAPEC-62, T1204
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 25, 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=< f828dc6
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
No public exploit references are available in this record.
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