Security readout for executives and security teams
Plain-English summary
CVE-2023-2200 is a GitLab CE/EE output-encoding flaw where an authenticated attacker could place HTML into an email address field. The reported impact is limited integrity compromise, not data theft or outage. Business urgency is moderate because exposed GitLab instances with untrusted users should be upgraded, but sources do not show active exploitation.
Executive priority
Handle in the normal vulnerability remediation queue, with earlier action for public or partner-accessible GitLab systems. The main risk is UI or email-content manipulation, not confirmed compromise.
Technical view
GitLab CE/EE versions from 7.14 before 15.11.10, 16.0 before 16.0.6, and 16.1 before 16.1.1 are affected. The flaw maps to CWE-116 and has CVSS 4.1: network reachable, low complexity, low privileges, user interaction required, scope changed, low integrity impact.
Likely exposure
Exposure is most relevant for GitLab CE/EE deployments in the affected version ranges, especially where low-privileged or external users can set email address values that other users later view.
Exploitation context
The bundle includes a HackerOne report and GitLab issue, but KEV is false and no source here states in-the-wild exploitation. Treat proof-of-concept detail as public, not proof of active attacks.
Researcher notes
Do not assume broad XSS or active exploitation beyond the cited issue. The available CVSS vector requires privileges and user interaction, with low integrity impact only. Evidence for patch guidance is limited to fixed version boundaries in the CVE description.
Mitigation direction
- Upgrade GitLab CE/EE to 15.11.10, 16.0.6, 16.1.1, or later fixed releases.
- Prioritize internet-facing or multi-tenant GitLab instances first.
- Review GitLab vendor guidance for any release-specific upgrade constraints.
- Restrict untrusted account creation where operationally feasible until upgraded.
Validation and detection
- Inventory GitLab CE/EE versions across all environments.
- Confirm affected instances are no longer below the fixed version thresholds.
- Check whether external or low-privileged users can modify email address fields.
- Review recent account profile changes for unexpected HTML-like content.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-116: User-session and phishing behavior lookup
Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2023-2200 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 4.1 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:N/I:L/A:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:N/I:L/A:N2.31.4Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
4.1MediumVector: CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:N/I:L/A:N
Source materials
- CVE List V5 sourceCVE List V5
- GitLab Issue #408281CVE reference · issue-tracking
- HackerOne Bug Bounty Report #1935628CVE reference · technical-description, exploit
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Encoding or Escaping of Output
Improper Encoding or Escaping of Output represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.