Stored XSS via unescaped watchlist edit summaries
Published Mar 19, 2020 · Updated Aug 5, 2024
Stored XSS in MediaWiki MobileFrontend REL1_31 through REL1_33 allows remote attackers to execute script via a crafted edit summary. SpecialMobileWatchlist passes stored summaries through Sanitizer::stripAllTags but places the result into HTML without context-appropriate escaping. Exploitation requires a user who watches the edited page to open the mobile watchlist feed, where the script runs within that user's wiki origin.
Summary
What happened
Stored XSS in MediaWiki MobileFrontend REL1_31 through REL1_33 allows remote attackers to execute script via a crafted edit summary. SpecialMobileWatchlist passes stored summaries through Sanitizer::stripAllTags but places the result into HTML without context-appropriate escaping. Exploitation requires a user who watches the edited page to open the mobile watchlist feed, where the script runs within that user's wiki origin.
The record
- CVE
- CVE-2019-15124
- Published
- Mar 19, 2020
- Updated
- Aug 5, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-79, T1059.007
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 19, 2020CVE publishedPublication date reported by the CVE source.
- Aug 5, 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.
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 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