CVE-2025-31140
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 stored XSS was possible on Cloud Profiles 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 · high confidenceStored cross-site scripting (XSS) vulnerability in JetBrains TeamCity versions prior to 2025.03 allows attackers to inject malicious JavaScript into the Cloud Profiles page, which is then executed in the browsers of other users viewing that page.
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.03CVSS 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.
-
Verify TeamCity is installedCheck if TeamCity server is running in your environment by accessing the web interface (default port 8111) or checking for TeamCity processesAffected if TeamCity is accessible in your environment
-
Determine the installed TeamCity versionNavigate to Administration > Server Administration > Server Configuration, or access the About page in the TeamCity web interface to view the exact version numberAffected if The displayed version is any version prior to 2025.03
-
Verify Cloud Profiles feature is accessibleCheck if the Cloud Profiles section exists in your TeamCity installation by navigating to Administration and looking for Cloud Profiles, or by checking if the path /admin/cloudProfiles is accessibleAffected if The Cloud Profiles feature exists and is accessible in your installation
Your environment is affected if you are running any version of JetBrains TeamCity prior to 2025.03 and the Cloud Profiles feature is available to users.
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
Upgrade TeamCity to version 2025.03 or later to remediate this stored XSS vulnerability.
2025.03
- Back up your current TeamCity installation, including the <TeamCity home> directory, database, and configuration files
- Download TeamCity version 2025.03 or later from the official JetBrains website (www.jetbrains.com/teamcity/download)
- Stop the running TeamCity server
- Follow the official TeamCity upgrade instructions to replace the existing installation with the new version
- Start the TeamCity server and verify it runs without errors
- Log in to TeamCity and navigate to the Cloud Profiles page to confirm the application loads correctly
- Test that the Cloud Profiles functionality works as expected after the upgrade
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-31140 — 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-31140 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