dbcve.org
TeamcityApplication · Jetbrains

CVE-2023-38061

MEDIUM · 5.4 CVSS v3.1 Published 2023-07-12
Fix available
A fix is available. Upgrade to 2023.05.1 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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.1 stored XSS when using a custom theme 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 confidence

A stored cross-site scripting (XSS) vulnerability exists in JetBrains TeamCity versions prior to 2023.05.1. The vulnerability specifically affects the custom theme functionality, allowing an attacker to inject malicious scripts that persist and execute when users interact with the custom-themed interface.

MitigationUpgrade JetBrains TeamCity to version 2023.05.1 or later to obtain the patch. If immediate upgrade is not possible, restrict or disable custom theme usage and implement Content Security Policy (CSP) headers as a defensive measure.

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.1

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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Determine installed TeamCity version
    Access the TeamCity server administration interface and navigate to 'Administration > Server Configuration' to view the current version, or check the buildServer.properties file in the TeamCity data directory for the version number
    Affected if The installed version is any release prior to 2023.05.1 (e.g., 2023.05, 2023.04.x, 2023.03.x, etc.)
  2. Verify custom theme functionality status
    Navigate to 'Administration > Server Configuration > Visual' in the TeamCity web interface and check if any custom themes have been created or enabled under the 'Custom theme' section
    Affected if Custom themes are enabled or any custom theme configurations exist on the server
  3. Inspect custom theme configurations for suspicious content
    Examine the theme XML or configuration files in the TeamCity data directory (typically under <TeamCity Data Directory>/config/_notifications or related theme storage locations) for any JavaScript tags, event handlers, or encoded script payloads
    Affected if Any custom theme contains script elements, onclick/onload handlers, or suspicious encoded content that does not belong to legitimate styling
  4. Review server logs for XSS indicators
    Check TeamCity server logs (teamcity-server.log) for patterns indicating XSS attempts such as '<script', 'javascript:', 'onerror=', 'onload=' within theme-related request parameters
    Affected if Logs contain requests with script injection patterns targeting theme-related endpoints

You are affected if your TeamCity version is older than 2023.05.1 AND custom theme functionality has been used on your server, as the stored XSS only executes when users interact with the custom-themed interface.

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.1 or later
Fixed in 2023.05.1
Interim mitigation

Upgrade JetBrains TeamCity to version 2023.05.1 or later to obtain the patch. If immediate upgrade is not possible, restrict or disable custom theme usage and implement Content Security Policy (CSP) headers as a defensive measure.

Recommended fix High confidence

2023.05.1

  1. Backup your TeamCity data directory before upgrading
  2. Download TeamCity 2023.05.1 or a later stable version from the official JetBrains website (www.jetbrains.com/teamcity/download)
  3. Stop the TeamCity server
  4. Follow the standard TeamCity upgrade procedure: run the installer or extract the new version to replace the existing installation
  5. Start the TeamCity server
  6. Verify the upgrade was successful by checking the TeamCity version in the administration area

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

Fix this in Teamcity Scoped from the published advisory
  • Consultation4.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,600
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,960.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-38061 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

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-38061 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