GitLabApplication
CVE-2022-1948
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 affecting all versions starting from 15.0 before 15.0.1. Missing validation of input used in quick actions allowed an attacker to exploit XSS by injecting HTML in contact details.
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 confidenceGitLab 15.0 before 15.0.1 fails to validate input in the quick actions feature related to contact details, allowing attackers to inject malicious HTML that executes as cross-site scripting (XSS) when other users view the contact information.
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.0.0CVSS 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 the command: gitlab-rake gitlab:env:info or check /opt/gitlab/versionAffected if The version displayed is exactly 15.0.0
-
Confirm the exact version numberRun: cat /opt/gitlab/embedded/service/gitlab-rails/VERSION or use the admin area web interface under Admin Area > Settings > GeneralAffected if The version is precisely 15.0.0 (not 15.0.1 or later, not 15.1 or other versions)
-
Verify quick actions feature is accessibleCheck if quick actions are available in issues, merge requests, or comments by viewing the quick actions reference documentation or testing in a test issueAffected if Quick actions feature is enabled and accessible to users (this is the default configuration)
-
Check for user-provided contact detailsReview user profiles, particularly any contact information fields that may have been set using quick actions like /contact or similar commandsAffected if Users have populated contact details in their profiles using quick actions and other users can view those profiles
You are affected if your GitLab instance is exactly version 15.0.0 and users have used quick actions to add contact details that could contain injected malicious HTML.
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 · scopedUpgrade GitLab to version 15.0.1 or later, which contains the fix for proper input validation in quick actions.
15.0.1
- Ensure you have a complete backup of your GitLab instance
- Plan for a maintenance window as the upgrade may require downtime
- For self-managed GitLab installations, follow the official upgrade documentation for your deployment method (Omnibus or source)
- Upgrade GitLab from version 15.0.0 to version 15.0.1 or later
- After upgrade, verify the quick actions feature works correctly in contact details
- Confirm the XSS vulnerability is resolved by testing that HTML cannot be injected into contact details via quick actions
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in GitLab
Scoped from the published advisory
- Consultation1.0 h
- Implementation1.0 h
- Testing2.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 $1,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-1948 — 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-1948 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