dbcve.org
GitLabApplication

CVE-2025-0376

MEDIUM · 6.1 CVSS v3.1 Published 2025-02-12
Fix available
A fix is available. Upgrade to 17.6.5 / 17.7.4 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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 · unedited
An XSS vulnerability exists in GitLab CE/EE affecting all versions from 13.3 prior to 17.6.5, 17.7 prior to 17.7.4 and 17.8 prior to 17.8.2 that allows an attacker to execute unauthorized actions via a change page.

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 confidence

Cross-site scripting (XSS) vulnerability in GitLab CE/EE allows attackers to inject malicious scripts through a change page, potentially executing unauthorized actions on behalf of authenticated users or stealing session credentials.

MitigationUpgrade GitLab to versions 17.6.5, 17.7.4, or 17.8.2 or later. Alternatively, implement input validation/output encoding as a compensating control if immediate upgrade is not feasible.

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
Affected:>= 13.3.0, < 17.6.5>= 17.7.0, < 17.7.4>= 17.8.0, < 17.8.2

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Check GitLab version in web interface
    Log into the GitLab instance as an administrator or user. Scroll to the footer of any GitLab page. The version number is displayed there (e.g., 'GitLab 17.8.1').
    Affected if The displayed version falls within any of these ranges: >= 13.3.0 and < 17.6.5, OR >= 17.7.0 and < 17.7.4, OR >= 17.8.0 and < 17.8.2.
  2. Check GitLab version via command line
    On the GitLab server, run `gitlab-rake gitlab:env:info` or `gitlab --version` to retrieve the installed version number.
    Affected if The command output shows a version matching any of these ranges: >= 13.3.0 and < 17.6.5, OR >= 17.7.0 and < 17.7.4, OR >= 17.8.0 and < 17.8.2.
  3. Check GitLab version via API
    Make an authenticated API request to `/api/v4/version` (e.g., `curl --header "PRIVATE-TOKEN: your_token" https://your-gitlab-instance/api/v4/version`). The response contains a `version` field.
    Affected if The API response version falls within any of the affected ranges listed above.

If any of the detection methods reveal a GitLab version matching the affected ranges (13.3.0 to 17.6.4, 17.7.0 to 17.7.3, or 17.8.0 to 17.8.1), the environment is vulnerable to this XSS flaw.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 17.6.5 / 17.7.4 / 17.8.2 or later
Fixed in 17.6.517.7.417.8.2
Interim mitigation

Upgrade GitLab to versions 17.6.5, 17.7.4, or 17.8.2 or later. Alternatively, implement input validation/output encoding as a compensating control if immediate upgrade is not feasible.

Recommended fix High confidence

Upgrade to GitLab 17.8.2 (or the latest 17.x stable release)

  1. 1. Back up your GitLab instance database and configuration files before proceeding with the upgrade
  2. 2. Review the GitLab upgrade documentation for your installation method (Omnibus, source, or Docker)
  3. 3. Plan appropriate maintenance window as upgrade may require downtime
  4. 4. For Omnibus installations: Update your package repository and install the new version using 'apt-get update' and 'apt-get install gitlab-ee' (or 'gitlab-ce')
  5. 5. For source installations: Clone the specific tag (e.g., v17.8.2) and follow the upgrade guide
  6. 6. After upgrade, run 'gitlab-ctl reconfigure' for Omnibus installations
  7. 7. Verify the upgrade was successful by checking the GitLab version in the Admin Area > Metrics and profiling > Version
  8. 8. Test that the change page functionality works correctly and no XSS payloads are executing
Caveat Review GitLab 17.8 release notes for any breaking changes, particularly regarding deprecated features and required database migrations that may extend upgrade time

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
18.0 hours of engineering $3,200
Get the upgrade done

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-0376 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-0376 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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