dbcve.org
TeamcityApplication · Jetbrains

CVE-2025-52876

MEDIUM · 5.4 CVSS v3.1 Published 2025-06-23
Fix available
A fix is available. Upgrade to 2025.03.3 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 2025.03.3 reflected XSS on the favoriteIcon 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 JetBrains TeamCity's favoriteIcon page allows attackers to inject malicious scripts via unsanitized user input, affecting versions prior to 2025.03.3.

MitigationUpgrade TeamCity to version 2025.03.3 or later to obtain the security patch.

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:< 2025.03.3

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. Locate TeamCity installation directory
    Check common installation paths such as /opt/TeamCity, /usr/local/TeamCity, or the directory where the TeamCity server is running. On Windows, check C:\TeamCity or the installation directory used during setup.
    Affected if TeamCity is installed on the system
  2. Identify installed TeamCity version
    Look for a version file in the TeamCity directory, typically found in <TeamCity_home>/build.txt or <TeamCity_home>/version.txt. Alternatively, log into the TeamCity web UI as an administrator and navigate to Administration > Server Administration > Server Configuration to view the build number.
    Affected if The version displayed is earlier than 2025.03.3 (e.g., 2025.03.2, 2025.02.x, or older)
  3. Verify favoriteIcon functionality is accessible
    Attempt to access the /favoriteIcon endpoint via URL in the TeamCity web interface, or check if the favoriteIcon feature is enabled in the TeamCity administration settings under General Settings or User Management.
    Affected if The favoriteIcon page is accessible without authentication restrictions or input validation is suspected to be missing
  4. Confirm version is within affected range
    Compare the identified build number against the vulnerable range: any version prior to 2025.03.3. If the version cannot be determined, assume affected until verified otherwise.
    Affected if Installed version is less than 2025.03.3 (e.g., 2025.03, 2025.02.1, 2024.x, etc.)

If TeamCity is running version 2025.03.3 or later, the environment is not affected; if running any version prior to 2025.03.3 and the favoriteIcon functionality is accessible, the environment is affected by this reflected XSS vulnerability.

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

Upgrade TeamCity to version 2025.03.3 or later to obtain the security patch.

Recommended fix High confidence

TeamCity 2025.03.3

  1. Verify current TeamCity version by navigating to Administration > Global Settings
  2. Download TeamCity 2025.03.3 or later from the official JetBrains website (www.jetbrains.com/teamcity/download)
  3. Create a complete backup of the TeamCity data directory and database
  4. Stop the TeamCity server service
  5. Extract and install the new version following the official upgrade documentation
  6. Start the TeamCity server service
  7. Verify the upgrade was successful by checking the version in Administration > Global Settings
  8. Confirm the favoriteIcon functionality works without XSS vulnerability

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

Fix this in Teamcity Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-52876 — 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-2025-52876 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