TeamcityApplication · Jetbrains

CVE-2023-34226

MEDIUM · 6.1 CVSS v3.1 Published 2023-05-31
Fix available
A fix is available. Upgrade to 2023.05 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
In JetBrains TeamCity before 2023.05 reflected XSS in the Subscriptions page 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 · high confidence

Reflected XSS vulnerability in the Subscriptions page of JetBrains TeamCity versions before 2023.05 allows attackers to inject malicious scripts via unsanitized user input that is reflected back in the server response, potentially executing in victim browsers.

MitigationUpgrade TeamCity to version 2023.05 or later which contains the fix. If immediate upgrade is not feasible, implement output encoding and input validation on the Subscriptions page as a compensating control.

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
TeamcityApplication
Affected:< 2023.05

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. Determine installed TeamCity version
    Navigate to the Administration > Diagnostics page or check the <TeamCity home>/logs/teamcity-server.log file for version information. Alternatively, access the /admin/admin.html?item=about page which displays the running TeamCity version.
    Affected if The displayed version is below 2023.05 (for example, 2023.04.x, 2022.x, or earlier)
  2. Verify the Subscriptions page is accessible
    Attempt to access the Subscriptions page at /admin/subscriptions.html or navigate to Administration > Subscriptions in the TeamCity web interface.
    Affected if The Subscriptions page loads and accepts user input, indicating the vulnerable feature is enabled and accessible
  3. Confirm version is within affected range
    Compare your identified version number to the affected range: versions before 2023.05. TeamCity versions follow a Year.Major.Minor pattern (e.g., 2023.04, 2022.12).
    Affected if Your installed TeamCity version is 2023.04.x or any earlier release (2022.x, 2021.x, etc.)

You are affected if your TeamCity installation version is below 2023.05 and the Subscriptions administrative page is accessible in your environment, as the reflected XSS vulnerability exists in that page in unpatched versions.

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 2023.05 or later
Fixed in 2023.05
Interim mitigation

Upgrade TeamCity to version 2023.05 or later which contains the fix. If immediate upgrade is not feasible, implement output encoding and input validation on the Subscriptions page as a compensating control.

Recommended fix High confidence

2023.05 or later

  1. Confirm current TeamCity version is below 2023.05 by checking the server administration UI or version file
  2. Review the official TeamCity 2023.05 release notes for upgrade requirements and any configuration changes
  3. Perform a full backup of the TeamCity server data directory and database
  4. Test the upgrade in a staging environment before applying to production
  5. Stop the TeamCity server
  6. Upgrade TeamCity to version 2023.05 or later following the standard upgrade procedure
  7. Verify the upgrade completed successfully and the server is operational
  8. Confirm the Subscriptions page is accessible and the XSS vulnerability is resolved
Caveat No specific breaking changes mentioned in the provided description; standard upgrade best practices apply

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Teamcity 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-2023-34226 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-34226 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