Stored XSS via unescaped message definitions
Published Jan 12, 2024 · Updated Jun 4, 2025
Stored XSS in MediaWiki CheckUser before 1.35.14, 1.36.0 through 1.39.5, and 1.40.0 through 1.40.1 allows remote authenticated users to run script. SpecialCheckUserLog renders interface-message definitions into HTML without neutralizing active markup. The attacker needs permission to edit MediaWiki interface messages, and execution requires another user to open an affected CheckUser log view.
Summary
What happened
Stored XSS in MediaWiki CheckUser before 1.35.14, 1.36.0 through 1.39.5, and 1.40.0 through 1.40.1 allows remote authenticated users to run script. SpecialCheckUserLog renders interface-message definitions into HTML without neutralizing active markup. The attacker needs permission to edit MediaWiki interface messages, and execution requires another user to open an affected CheckUser log view.
The record
- CVE
- CVE-2024-23172
- Published
- Jan 12, 2024
- Updated
- Jun 4, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-79, T1203
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jan 12, 2024CVE publishedPublication date reported by the CVE source.
- Jun 4, 2025Record 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.
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
- Wikimedia Phabricator XSS reproductionproof of concept · unverified
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