GitLabApplication
CVE-2022-4007
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 · uneditedA issue has been discovered in GitLab CE/EE affecting all versions from 15.3 prior to 15.7.8, version 15.8 prior to 15.8.4, and version 15.9 prior to 15.9.2 A cross-site scripting vulnerability was found in the title field of work items that allowed attackers to perform arbitrary actions on behalf of victims at client side.
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 confidenceA stored cross-site scripting (XSS) vulnerability in GitLab CE/EE allows attackers to inject malicious JavaScript into the title field of work items. When victims view these work items, the injected script executes in their browsers, enabling session hijacking, data theft, or performing actions on behalf of authenticated users.
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
>= 15.3, < 15.7.8>= 15.8.0, < 15.8.4>= 15.9.0, < 15.9.2CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Determine installed GitLab versionRun `sudo gitlab-rake gitlab:env:info` or check the GitLab admin area under '/help' to find the exact version numberAffected if The installed version falls within any of these ranges: >= 15.3 and < 15.7.8, OR >= 15.8.0 and < 15.8.4, OR >= 15.9.0 and < 15.9.2
-
Confirm work items feature is accessibleVerify that work items are available in the GitLab instance by navigating to a project and checking if the 'Work items' menu option exists under the Issues sectionAffected if Work items functionality is present and accessible to users in the GitLab instance
-
Identify any work items with unexpected title contentQuery the database for work item titles containing HTML or script tags, or inspect work items via the API endpoint `/projects/:id/work_items`Affected if Any work item titles contain unsanitized HTML, script tags, or javascript: URIs that could indicate exploitation
A user is affected if their GitLab version is within the affected ranges listed above AND the work items feature is accessible in their instance, regardless of whether malicious work items are currently present.
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.7.815.8.415.9.2
Upgrade GitLab to version 15.7.8, 15.8.4, or 15.9.2 or later to receive the patch that properly sanitizes work item title fields.
Upgrade to GitLab 15.7.8, 15.8.4, 15.9.2, or later
- 1. Identify your current GitLab version by navigating to the GitLab admin area or running `gitlab-rake gitlab:env:info`
- 2. Based on your current version, upgrade to the appropriate fixed release: 15.7.8, 15.8.4, or 15.9.2 (or a later version)
- 3. Follow the standard GitLab upgrade documentation for your installation method (omnibus, source, or Helm chart)
- 4. Ensure database migrations complete successfully during the upgrade
- 5. Verify the upgrade by checking the GitLab version at /help or via admin area
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in GitLab
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing3.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,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-4007 — 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-2022-4007 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