Stored XSS via insufficient wiki page validation
Published Mar 10, 2020 · Updated Aug 4, 2024
Stored XSS in GitLab Community and Enterprise Edition 8.9 through 11.11 allows remote attackers to inject script into wiki pages. Wiki page input is persisted without sufficient validation, allowing attacker-controlled content to execute as script when another user opens the affected page. Exploitation requires another user to view the stored page; successful execution can read or alter data available to that user's browser session.
Summary
What happened
Stored XSS in GitLab Community and Enterprise Edition 8.9 through 11.11 allows remote attackers to inject script into wiki pages. Wiki page input is persisted without sufficient validation, allowing attacker-controlled content to execute as script when another user opens the affected page. Exploitation requires another user to view the stored page; successful execution can read or alter data available to that user's browser session.
The record
- CVE
- CVE-2019-12444
- Published
- Mar 10, 2020
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-79, T1059.007
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 10, 2020CVE publishedPublication date reported by the CVE source.
- Aug 4, 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
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