GitLabApplication
CVE-2019-15739
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedAn issue was discovered in GitLab Community and Enterprise Edition 8.1 through 12.2.1. Certain areas displaying Markdown were not properly sanitizing some XSS payloads.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceA stored Cross-Site Scripting (XSS) vulnerability exists in GitLab Community and Enterprise Edition versions 8.1 through 12.2.1. Certain areas that display Markdown content fail to properly sanitize malicious XSS payloads, allowing attackers to inject and execute arbitrary JavaScript in the browsers of users viewing the affected Markdown content.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
GitLabApplication
>= 8.1.0, < 12.0.8>= 12.1.0, < 12.1.8>= 12.2.0, < 12.2.3CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify installed GitLab versionRun 'cat /opt/gitlab/version' on the GitLab server, or log into the GitLab Admin area and navigate to the Admin > Overview > Dashboard page to view the current version number.Affected if The installed version is 8.1.0 through 12.0.7, 12.1.0 through 12.1.7, or 12.2.0 through 12.2.2 (versions prior to the fixed releases).
-
Confirm GitLab editionCheck the GitLab Admin > Overview > Dashboard page or the footer of any GitLab page to determine if you are running Community Edition (CE) or Enterprise Edition (EE).Affected if Both Community and Enterprise Edition are affected by this CVE.
-
Determine if Markdown content areas are in useReview which GitLab features with Markdown rendering are accessible in your instance: projects, issues, merge requests, comments, wiki pages, and snippets. Check if untrusted users can create or edit content in these areas.Affected if The vulnerability only applies where Markdown content is displayed to users without sanitization.
-
Audit existing Markdown content for suspicious payloadsSearch GitLab database tables (such as notes, issues, merge_requests, snippets, and wikis) for patterns like <script>, javascript:, onerror=, onload=, or other HTML/JS attributes that may indicate injected XSS payloads.Affected if Malicious JavaScript or HTML injection payloads are found in any Markdown-stored content.
You are affected if your GitLab version is 8.1.0 to 12.0.7, 12.1.0 to 12.1.7, or 12.2.0 to 12.2.2 AND your instance renders Markdown content that could contain user-supplied input.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor data12.0.812.1.812.2.3
Upgrade GitLab to version 12.2.2 or later. If immediate patching is not possible, restrict or sanitize Markdown input in affected areas until the upgrade can be completed.
Fix this in GitLab
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-15739 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2019-15739 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data