GitLabApplication
CVE-2023-2200
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 has been discovered in GitLab CE/EE affecting all versions starting from 7.14 before 15.11.10, all versions starting from 16.0 before 16.0.6, all versions starting from 16.1 before 16.1.1, which allows an attacker to inject HTML in an email address field.
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 confidenceThis is a cross-site scripting (XSS) vulnerability in GitLab CE/EE where an attacker can inject malicious HTML into an email address field. The flaw exists due to insufficient input validation/sanitization on the email field, allowing stored XSS to occur when the injected HTML is rendered in the application.
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
>= 7.14.0, < 15.11.10>= 16.0.0, < 16.0.6>= 16.1.0, < 16.1.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 the installed GitLab versionRun command: `sudo gitlab-rake gitlab:env:info` or check the Admin Area > Dashboard > Information section in the web UI. The version is displayed near the top.Affected if The version falls within any of these ranges: 7.14.0 to 15.11.9, 16.0.0 to 16.0.5, or 16.1.0.
-
Verify if user registration or profile editing is accessibleCheck if the 'Sign-up enabled' setting is active in Admin Area > Settings > General > Sign-up restrictions, or if authenticated users can edit their own email addresses in their profile settings.Affected if User registration is enabled or users can modify their own email addresses in the application.
-
Review user profiles for suspicious email addressesNavigate to Admin Area > Users and examine the email addresses listed for each user. Look for email addresses containing HTML tags such as <script>, <img>, or javascript: URIs, or addresses with unusual characters that may indicate injection attempts.Affected if Any user account has an email address containing HTML markup, script tags, or encoded characters that do not belong in a valid email address.
You are affected if your GitLab version is less than 15.11.10, 16.0.6, or 16.1.1 AND user registration or profile email editing is enabled, or if you already see malformed email addresses in user accounts.
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.
dbcve · scoped15.11.1016.0.616.1.1
Upgrade GitLab to version 15.11.10, 16.0.6, 16.1.1 or later to patch the vulnerability. Until then, restrict user registration or carefully review user profiles for suspicious email addresses.
16.1.1 or later (15.11.10 for 15.11.x line, 16.0.6 for 16.0.x line, 16.1.1 for 16.1.x line)
- 1. Back up your GitLab instance database and configuration
- 2. Schedule a maintenance window for the upgrade
- 3. For GitLab installations using omnibus packages: run 'sudo apt-get update && sudo apt-get install gitlab-ce' (or gitlab-ee for Enterprise Edition)
- 4. For installations from source: stop GitLab, pull the fixed version (16.1.1 or later), run bundle install, db:migrate, and restart services
- 5. Verify the upgrade completed successfully by checking the GitLab admin area and version number
- 6. Test that email address fields properly escape HTML characters
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in GitLab
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-2200 — 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-2023-2200 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