CVE-2023-34222
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 2023.05 possible XSS in the Plugin Vendor URL 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 confidenceA stored Cross-Site Scripting (XSS) vulnerability exists in JetBrains TeamCity versions prior to 2023.05. The vulnerability is located in the Plugin Vendor URL field, where malicious JavaScript code can be injected and executed when other users view the plugin.
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< 2023.05CVSS 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.
-
Check installed TeamCity versionNavigate to Administration > Server Administration > Server Configuration, or access /admin/serverDiagnostics.html, and locate the version number displayed.Affected if The displayed version is earlier than 2023.05 (for example, 2023.04.4, 2023.03, 2022.x, etc.)
-
Access plugin administrationGo to Administration > Plugins to view the list of installed plugins.Affected if You have access to the plugin management interface.
-
Inspect Plugin Vendor URL fieldsClick on each installed plugin and examine the Vendor URL field in the plugin details. Look for any URL values containing JavaScript: or script tags, or unusual encoded characters.Affected if The Vendor URL field contains executable JavaScript code or suspicious script content that was not entered by an administrator.
-
Verify if plugins are visible to other usersLog out or use an alternate user account to view the plugin list as a non-administrator user, then navigate to the plugin page.Affected if Other users can view the plugin details page where the malicious Vendor URL would execute.
You are affected if your TeamCity version is earlier than 2023.05 AND a plugin contains malicious JavaScript code in its Vendor URL field that could execute when viewed by other users.
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 · scoped2023.05
Update JetBrains TeamCity to version 2023.05 or later to remediate this vulnerability.
2023.05
- Upgrade TeamCity to version 2023.05 or later to resolve the XSS vulnerability in the Plugin Vendor URL
- Verify the upgrade was successful and the vulnerability is mitigated
- Test that plugins with Vendor URLs function correctly after the upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-34222 — 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-2023-34222 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