CVE-2020-7910
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 · uneditedJetBrains TeamCity before 2019.2 was vulnerable to a stored XSS attack by a user with the developer role.
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 XSS vulnerability in JetBrains TeamCity versions prior to 2019.2 allows authenticated users with the developer role to inject malicious scripts into the application that execute when viewed by other users.
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< 2019.2.0CVSS 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.
-
Locate your TeamCity version numberAccess the TeamCity Administration > Diagnostics page or check the version.txt file in the TeamCity data directory. The version is also displayed on the login page and in the Administration > Global Settings section.Affected if The installed version is any release prior to 2019.2.0 (for example, 2019.1.x, 2018.x, or earlier)
-
Confirm the vulnerable version is in useCompare your identified version against the affected range. TeamCity versions follow a major.minor.patch format.Affected if The version string starts with a number lower than 2019.2, such as 2019.1, 2018.2, 2018.1, or any earlier release
-
Identify users with developer roleNavigate to Administration > User Management > Users and examine the roles assigned to each user account. Look for any account listed with the 'Developer' role in the roles column.Affected if Any user account in your TeamCity instance is assigned the Developer role, as this role is required to inject the malicious script
-
Audit custom build configurations or project settingsReview build configurations, project parameters, and VCS settings for any recently added or modified entries that contain unexpected script tags, JavaScript URIs, or HTML markup in fields that accept user input.Affected if You discover scripts or HTML tags embedded in fields that normal users did not create, indicating potential exploitation
Your environment is affected if the installed TeamCity version is below 2019.2.0 and you have users assigned the Developer role, as both conditions are required for this stored XSS to be exploitable.
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.
From vendor data2019.2.0
Upgrade TeamCity to version 2019.2 or later which contains the security patch for this vulnerability.
- Consultation2.0 h
- Implementation4.0 h
- Testing4.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,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-7910 — 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-2020-7910 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