CVE-2025-24459
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 2024.12.1 reflected XSS was possible on the Vault Connection page
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 confidenceReflected XSS vulnerability in JetBrains TeamCity's Vault Connection page allows attackers to inject malicious JavaScript through unsanitized user input that is reflected back in the HTTP response. This affects versions before 2024.12.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< 2024.12.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.
-
Check TeamCity server versionLog in to TeamCity as administrator and navigate to Administration > Server Administration > Server Information, or access the version via REST API at /app/rest/server/versionAffected if The displayed version number is lower than 2024.12.1 (for example, 2024.11.2, 2024.10.0, etc.)
-
Verify Vault Connection page accessibilityNavigate to Administration > Integrations > Vault Connections (or the corresponding Vault settings page in your TeamCity version)Affected if The Vault Connection configuration page loads and accepts user input, indicating the feature is enabled
-
Test for XSS vulnerability in Vault Connection parametersSubmit a test payload containing a benign script tag (such as <script>alert('test')</script>) in the Vault Connection form fields (server URL, connection name, or other text inputs) and observe whether the input is reflected back unescaped in the responseAffected if The submitted payload is reflected back in the HTML response without proper encoding or sanitization, demonstrating the XSS vulnerability exists
Your TeamCity installation is affected if the installed version is below 2024.12.1 AND the Vault Connection feature is accessible and reflects unsanitized user input in the HTTP response.
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 · scoped2024.12.1
Upgrade TeamCity to version 2024.12.1 or later which contains the fix for this vulnerability.
2024.12.1
- Backup your TeamCity data and configuration before upgrading
- Download TeamCity 2024.12.1 or later from the official JetBrains website
- Stop the TeamCity server
- Install the new version following the standard upgrade procedure
- Start the TeamCity server and verify the Vault Connection page is accessible
- Verify the XSS vulnerability is no longer present by testing the Vault Connection page input fields
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-24459 — 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-24459 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