CVE-2022-48426
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 · uneditedIn JetBrains TeamCity before 2022.10.3 stored XSS in Perforce connection settings was possible
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 confidenceStored XSS vulnerability in JetBrains TeamCity's Perforce connection settings allows authenticated users with configuration access to inject malicious scripts that execute when other users view the Perforce connection configuration.
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= 2022.10.3CVSS 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.
-
Check installed TeamCity versionNavigate to Administration > Server Configuration > Server Info in the TeamCity web UI, or check the version banner on the login page. Alternatively, inspect the TeamCity installation directory for a version file.Affected if The installed version is earlier than 2022.10.3 (any version from 2022.10.0 through 2022.10.2, or older major releases)
-
Verify Perforce connection is configuredNavigate to Administration > VCS Roots in the TeamCity web UI. Look for any VCS root configured with the Perforce connection type.Affected if A Perforce VCS root exists and is actively used by builds
-
Check user permissions for VCS configurationNavigate to Administration > User Management > Users or Groups. Verify if the account you use has permission to create or edit VCS roots (typically 'Edit project' or 'Create VCS root' permissions).Affected if Your user account has privileges to modify Perforce connection settings
-
Inspect Perforce connection configuration for scriptsNavigate to the Perforce VCS root settings page. Examine the fields (especially connection parameters, depot paths, or custom fields) for any unexpected HTML or JavaScript content.Affected if Malicious script tags or event handlers are present in any Perforce configuration field
You are affected if your TeamCity version is before 2022.10.3 AND you have a configured Perforce connection that users can view without elevated privileges.
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 TeamCity to version 2022.10.3 or later which contains the fix for this stored XSS vulnerability in Perforce connection settings.
TeamCity 2022.10.4 or later (any version after 2022.10.3)
- 1. Back up your current TeamCity data and configuration
- 2. Download TeamCity 2022.10.4 or later from the official JetBrains website (www.jetbrains.com/teamcity/download)
- 3. Stop the TeamCity server
- 4. Install the new version following the standard TeamCity upgrade procedure
- 5. Start the TeamCity server and verify all services are running
- 6. Log in to TeamCity and navigate to Administration > Connections
- 7. Verify the Perforce connection settings are accessible and test the connection
- 8. Confirm the XSS vulnerability in Perforce connection settings is resolved
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.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 $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-48426 — 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-48426 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