CVE-2022-25261
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 2021.2.2 was vulnerable to reflected XSS.
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 versions before 2021.2.2. The vulnerability allows attackers to inject malicious scripts through unsanitized user input that gets reflected back in the application's response, potentially executing in victim browsers.
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< 2021.2.2CVSS 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.
-
Locate TeamCity version in administration interfaceLog into the TeamCity web interface as an administrator and navigate to the Administration > Server Administration > About page. The installed version number is displayed there.Affected if The displayed version number is lower than 2021.2.2 (for example, 2021.2.1, 2021.1.x, or earlier)
-
Check version from server configuration filesInspect the TeamCity server configuration directory for version information. On the server file system, look in the TeamCity installation directory for a version file or check the main config file that contains build agent and server metadata.Affected if The version found in configuration files is less than 2021.2.2
-
Review server logs for version disclosureExamine the TeamCity server logs located in the logs directory. The startup logs typically contain the TeamCity version number during server initialization.Affected if The logged version at startup is below 2021.2.2
You are affected if your installed TeamCity version is any release prior to 2021.2.2, as this is a reflected XSS vulnerability present only in those earlier versions.
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 · scoped2021.2.2
Upgrade JetBrains TeamCity to version 2021.2.2 or later to obtain the patch for this reflected XSS vulnerability.
TeamCity 2021.2.2 or later
- Back up your TeamCity data and configuration before upgrading
- Download TeamCity 2021.2.2 or a later stable version from the official JetBrains website
- Stop the TeamCity server
- Install the new version following the standard TeamCity upgrade procedure
- Start the TeamCity server and verify the upgrade was successful
- Test that the XSS vulnerability is no longer present by reviewing the fix in the release notes
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.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 $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-25261 — 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-2022-25261 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