CVE-2025-46618
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.1 stored XSS was possible on Data Directory tab
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 confidenceA stored cross-site scripting (XSS) vulnerability in JetBrains TeamCity's Data Directory settings page allows authenticated administrators to inject malicious JavaScript that executes when other users view this configuration panel. The vulnerability exists in versions prior to 2025.03.1.
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.1CVSS 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
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/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.
-
Determine installed TeamCity versionAccess the TeamCity UI and navigate to the 'About' page (typically found under Administration > Server Administration > About), or check for a version.txt file in the TeamCity installation directory.Affected if The displayed version is lower than 2025.03.1 (for example, 2025.02.4 or earlier).
-
Verify Data Directory settings accessLog in as an administrator and navigate to Administration > Server Administration > Data Directory to confirm access to this configuration panel.Affected if The Data Directory settings page is accessible to administrators in your installation.
-
Inspect Data Directory configuration for suspicious contentExamine the Data Directory configuration files (typically stored in the <TeamCity Data Directory>/config directory) or view the Data Directory settings through the UI to identify any unexpected script tags, event handlers, or encoded JavaScript that could indicate XSS payload injection.Affected if The Data Directory configuration contains unencoded or encoded JavaScript, script tags, or suspicious attributes (such as onload, onerror, onmouseover event handlers) that were not intentionally configured by your administrators.
-
Review recent administrative configuration changesCheck TeamCity audit logs (if available) for recent modifications to the Data Directory settings, noting who made the changes and what values were submitted.Affected if Recent Data Directory configuration changes show unexpected or obfuscated content submitted by an administrator account.
Your environment is affected if you are running TeamCity version lower than 2025.03.1 and administrators have access to the Data Directory settings page where malicious script payloads could be stored and executed.
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.1
Upgrade TeamCity to version 2025.03.1 or later. As a defensive measure, implement output encoding when rendering any user-supplied data in the Data Directory interface and restrict administrative access to trusted personnel.
2025.03.1
- 1. Back up your TeamCity data directory and database before upgrading
- 2. Download TeamCity version 2025.03.1 or later from the official JetBrains website (www.jetbrains.com/teamcity/download)
- 3. Stop the TeamCity server gracefully
- 4. Install the new TeamCity version, following the standard upgrade procedure
- 5. Start the TeamCity server
- 6. Verify the Data Directory tab functions correctly and the XSS vulnerability is no longer present
- 7. Review server logs for any errors during startup
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-46618 — 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-46618 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