CVE-2025-47852
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 2025.03.2 stored XSS via YouTrack 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 confidenceStored cross-site scripting (XSS) vulnerability in JetBrains TeamCity's YouTrack integration allows authenticated attackers to inject malicious scripts that persist on the server and execute in browsers of other users viewing the affected content. The vulnerability exists in versions prior to 2025.03.2.
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< 2025.03.2CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Verify TeamCity server versionLog into the TeamCity web interface and navigate to Administration > Server Administration > Server Configuration, or check the version displayed on the login page. Alternatively, examine the <TeamCity home>/logs/teamcity-server.log file for version information at startup.Affected if The installed version is any release prior to 2025.03.2 (for example, 2025.03.1, 2024.x, or earlier)
-
Confirm YouTrack integration is activeNavigate to Administration > Integrations > YouTrack in the TeamCity web UI, or inspect the <TeamCity data directory>/config/YouTrack directory for configuration files.Affected if The YouTrack integration plugin is installed and has at least one project configured to sync with a YouTrack server
-
Check for existing injected contentReview build configurations, commits, or issues that display YouTrack data within TeamCity for any unexpected script tags, javascript: URIs, or HTML markup in fields that should contain plain text.Affected if Any stored XSS payloads are present in YouTrack-linked fields or comments visible to other users
A user is affected if their TeamCity version is below 2025.03.2 AND the YouTrack integration feature is enabled with configured connections.
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 · scoped2025.03.2
Upgrade TeamCity to version 2025.03.2 or later to obtain the patch for this stored XSS vulnerability in the YouTrack integration feature.
TeamCity 2025.03.2 or later
- 1. Back up your current TeamCity configuration and data
- 2. Download TeamCity 2025.03.2 or later from the official JetBrains website
- 3. Stop the TeamCity server
- 4. Follow the standard TeamCity upgrade procedure for your installation method
- 5. Start the TeamCity server after upgrade
- 6. Verify the YouTrack integration functionality works correctly
- 7. Confirm the XSS vulnerability is resolved by testing the YouTrack integration with potentially malicious input
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing6.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 $3,808.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-47852 — 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-2025-47852 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