dbcve.org
TeamcityApplication · Jetbrains

CVE-2025-47853

MEDIUM · 5.4 CVSS v3.1 Published 2025-05-20
Fix available
A fix is available. Upgrade to 2025.03.2 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.2 stored XSS via Jira integration 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

Stored Cross-Site Scripting (XSS) vulnerability in JetBrains TeamCity's Jira integration feature. Attackers could inject malicious scripts into Jira-related fields that would be stored and executed when other users view the affected content in TeamCity.

MitigationUpgrade JetBrains TeamCity to version 2025.03.2 or later to remediate this vulnerability.

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

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. Check TeamCity version
    Navigate to Administration > About in the TeamCity web UI, or locate the version.txt file in the TeamCity installation or data directory
    Affected if The installed version is earlier than 2025.03.2
  2. Verify Jira integration is configured
    Navigate to Administration > Integrations and check if Jira or Jira-related issue tracker connections are enabled and configured
    Affected if Jira integration is active and the TeamCity version is below 2025.03.2
  3. Inspect Jira connection settings
    Review any Jira server connections, project mappings, or issue tracker configurations in the TeamCity administration area
    Affected if Jira connections exist and the TeamCity version is below 2025.03.2

A TeamCity installation with Jira integration enabled running any version prior to 2025.03.2 is affected by this stored 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.2 or later
Fixed in 2025.03.2
Interim mitigation

Upgrade JetBrains TeamCity to version 2025.03.2 or later to remediate this vulnerability.

Recommended fix High confidence

TeamCity 2025.03.2

  1. Back up your TeamCity configuration and database before upgrading
  2. Download TeamCity 2025.03.2 or a later stable release from the official JetBrains website (www.jetbrains.com/teamcity/download)
  3. Stop the TeamCity server
  4. Install the upgrade following the standard TeamCity upgrade procedure
  5. Start the TeamCity server
  6. Verify that the Jira integration is functioning correctly after the upgrade

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

Fix this in Teamcity Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

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 locally
dbcve dependency scanner

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