LiveActive security incident?Get immediate response
CVE Record

CVE-2024-2279: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in GitLab

An issue has been discovered in GitLab CE/EE affecting all versions starting from 16.7 to 16.8.6 all versions starting from 16.9 before 16.9.4, all versions starting from 16.10 before 16.10.2. Using the autocomplete for issues references feature a crafted payload may lead to a stored XSS, allowing attackers to perform arbitrary actions on behalf of victims.

HighCVSS 8.7Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

GitLab CE/EE had a stored cross-site scripting flaw in issue-reference autocomplete. An authenticated attacker could plant content that runs when a victim interacts with the affected feature, potentially performing actions as that victim. Treat this as high priority for self-managed GitLab instances in the listed version ranges.

Executive priority

Prioritize remediation for internet-accessible or broadly used GitLab instances. The business risk is unauthorized actions through trusted user sessions, which can affect source code, project settings, and sensitive development workflows.

Technical view

CVE-2024-2279 is CWE-79 stored XSS affecting GitLab CE/EE 16.7 through 16.8.6, 16.9 before 16.9.4, and 16.10 before 16.10.2. The CVSS 3.1 score is 8.7 with network attack vector, low complexity, low privileges required, user interaction required, and changed scope.

Likely exposure

Exposure is most likely in self-managed GitLab CE/EE deployments running the affected 16.7, 16.8, 16.9, or 16.10 ranges. GitLab.com exposure is not stated in the provided sources.

Exploitation context

The provided sources do not show CISA KEV listing or confirmed active exploitation. The vulnerability requires attacker privileges and victim interaction, but stored XSS can be serious because successful execution may act in the victim’s GitLab session.

Researcher notes

Public technical evidence is limited because the GitLab issue and HackerOne report are marked permissions-required in the source bundle. Do not assume exploit details beyond stored XSS via issue-reference autocomplete and arbitrary victim-session actions stated in the CVE description.

Mitigation direction

  • Identify all GitLab CE/EE instances and record exact versions.
  • Upgrade affected 16.7, 16.8, 16.9, and 16.10 deployments outside the listed vulnerable ranges.
  • Review GitLab vendor guidance before scheduling production remediation.
  • Limit GitLab access to trusted users until remediation is complete.
  • Monitor GitLab audit logs for unusual user actions.

Validation and detection

  • Confirm whether installed versions match the affected ranges.
  • Verify upgraded instances report versions outside the vulnerable ranges.
  • Review recent issue-reference autocomplete activity where logs or telemetry allow.
  • Check for unexpected project, issue, token, membership, or settings changes.
  • Confirm no vulnerable test or staging GitLab instances remain exposed.
Prepared
Confidence
medium
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

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 · medium confidence lookup

CWE-79: 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 lookup
cve · low confidence lookup

CVE-2024-2279 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
8.7 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:N

Official CVE source material

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.

1CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS vector scores

1 official score

We 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.

ScoreVersionSeverityVectorExploitImpactSource
8.7CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:N2.35.8Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

8.7High
CVSS 3.1 vector shape for CVE-2024-2279Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
GitLabGitLab16.7, 16.9, 16.10unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.