CVE-2025-52875
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.3 a DOM-based XSS at the Performance Monitor 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 · moderate confidenceA DOM-based cross-site scripting (XSS) vulnerability exists in the Performance Monitor page of JetBrains TeamCity versions prior to 2025.03.3. The vulnerability allows attackers to inject malicious JavaScript code that executes in the context of the victim's browser through manipulation of the Document Object Model (DOM).
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.3CVSS 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.
-
Identify your TeamCity versionLocate the installed TeamCity version number (typically shown in the administration UI or server startup logs)Affected if The installed version is any release prior to 2025.03.3 (e.g., 2025.03.2, 2025.02.x, earlier versions)
-
Confirm access to the Performance Monitor pageNavigate to the Performance Monitor page in the TeamCity web interface or locate its URL pathAffected if The Performance Monitor page is accessible without additional restrictions beyond standard authentication
-
Verify user roles with Performance Monitor accessReview which user roles or groups are permitted to access the Performance Monitor functionalityAffected if Users beyond authenticated administrators have access to the Performance Monitor page
Your environment is affected if you are running any TeamCity version below 2025.03.3 and the Performance Monitor page is accessible to users beyond authenticated administrators.
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.3
Upgrade TeamCity to version 2025.03.3 or later. Until upgrade is possible, restrict access to the Performance Monitor page to authenticated administrators only.
TeamCity 2025.03.3
- Back up the TeamCity database and configuration files before starting the upgrade
- Download TeamCity 2025.03.3 or later from the official JetBrains website
- Stop the TeamCity server service
- Install the TeamCity upgrade following the official upgrade documentation at www.jetbrains.com/teamcity/docs
- Start the TeamCity server after installation completes
- Log in to the TeamCity web interface and navigate to the Performance Monitor page to verify the fix is applied
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation6.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-52875 — 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-52875 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