GitLabApplication
CVE-2019-19311
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 · uneditedGitLab EE 8.14 through 12.5, 12.4.3, and 12.3.6 allows XSS in group and profile fields.
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 · high confidenceGitLab EE versions 8.14 through 12.5, 12.4.3, and 12.3.6 contain a stored Cross-Site Scripting (XSS) vulnerability in group and profile fields. User-supplied input in these fields is not properly sanitized or encoded when rendered, allowing malicious scripts to execute in the browsers of other users viewing these fields.
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.14.0, < 12.3.7>= 12.4.0, < 12.4.4>= 12.5.0, < 12.5.1CVSS 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
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/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 GitLab versionCheck the installed GitLab version by accessing the Admin area (Navigate to /admin) or by running `gitlab-rake gitlab:env:info` on the server. The version is typically displayed on the Admin Dashboard or in the environment information output.Affected if The installed version falls within any of these ranges: 8.14.0 to 12.3.6, 12.4.0 to 12.4.3, or 12.5.0 (all 12.5.x versions below 12.5.1)
-
Confirm GitLab edition is EEVerify that the installed instance is GitLab Enterprise Edition (EE), not Community Edition (CE). This is visible in the Admin Dashboard under the GitLab version information or via `gitlab-rake gitlab:env:info` which displays the edition.Affected if The instance is GitLab EE (Enterprise Edition)
-
Check for accessible group and profile fieldsLog in as a regular user (non-admin) and navigate to user profile settings (click user avatar, select Settings > Profile) and group settings (create or select a group, go to Settings > General). Determine if these fields are accessible for input.Affected if The group and profile fields are accessible and editable by users in the instance
-
Verify XSS payload executionAs a test user, inject a benign XSS test payload into a group or profile field (such as `<script>alert('XSS')</script>` or an img onerror attribute). Save the field, then view the field as a different user or in a different browser context. Check if the script executes.Affected if The injected script executes when other users view the profile or group page containing the crafted field value
You are affected if your GitLab EE version is between 8.14.0 and 12.3.6, between 12.4.0 and 12.4.3, or 12.5.0, and users can inject and store malicious scripts in group or profile fields that execute in other users browsers.
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.3.712.4.412.5.1
Upgrade to a patched GitLab version. As an interim control, implement proper output encoding and input validation on group and profile field rendering, or restrict field input through a WAF with XSS rules.
Fix this in GitLab
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing2.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,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-19311 — 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-19311 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