Requester impersonation via cross-wiki actor ID collision
Published Oct 9, 2024 · Updated Oct 9, 2024
Improper ownership management in Miraheze ImportDump allows remote authenticated users to impersonate import requesters across wikis. The SpecialRequestImportQueue page trusts a requester actor ID stored without its originating wiki, so an equal local ID on another wiki is treated as the owner. Exploitation requires a logged-in account with a colliding actor ID and permits viewing private requests, adding comments, or editing the original requester's entry.
Summary
What happened
Improper ownership management in Miraheze ImportDump allows remote authenticated users to impersonate import requesters across wikis. The SpecialRequestImportQueue page trusts a requester actor ID stored without its originating wiki, so an equal local ID on another wiki is treated as the owner. Exploitation requires a logged-in account with a colliding actor ID and permits viewing private requests, adding comments, or editing the original requester's entry.
The record
- CVE
- CVE-2024-47816
- Published
- Oct 9, 2024
- Updated
- Oct 9, 2024
- Vendor
- Miraheze
- Product
- ImportDump
- Classifications
- CWE-282, T1190
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Oct 9, 2024CVE publishedPublication date reported by the CVE source.
- Oct 9, 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=commits prior to 5c91dfc
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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