Hidden-username disclosure via missing suppression check
Published Jun 30, 2023 · Updated Nov 27, 2024
Incorrect authorization in MediaWiki CheckUser through 1.39.3 allows remote authenticated users to read hidden usernames through its log API. The CheckUserLog API returns the stored target name without checking whether the account is hidden or whether the caller has the hideuser right. Access requires the checkuser-log right but not suppression rights, exposing hidden account names without granting broader log access.
Summary
What happened
Incorrect authorization in MediaWiki CheckUser through 1.39.3 allows remote authenticated users to read hidden usernames through its log API. The CheckUserLog API returns the stored target name without checking whether the account is hidden or whether the caller has the hideuser right. Access requires the checkuser-log right but not suppression rights, exposing hidden account names without granting broader log access.
The record
- CVE
- CVE-2023-37300
- Published
- Jun 30, 2023
- Updated
- Nov 27, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-863, T1213
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 30, 2023CVE publishedPublication date reported by the CVE source.
- Nov 27, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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.
Public exploit references
- Wikimedia CheckUserLog API reproduction stepsproof 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