CVE-2024-47951
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.07.3 stored XSS was possible via server global settings
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 confidenceStored XSS vulnerability in JetBrains TeamCity server global settings allows attackers to inject malicious scripts that execute when administrators view the affected settings. The vulnerability exists in versions prior to 2024.07.3.
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.07.3CVSS 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.
-
Check TeamCity server versionNavigate to Administration > Server Administration > Server Configuration or access the /admin/serverDiagnostics.html endpoint to view the installed version numberAffected if The displayed version is below 2024.07.3 (for example, 2024.07.2, 2024.06.x, earlier versions)
-
Access global settings areaLog into TeamCity as an administrator and navigate to Administration > Server Configuration > Global Settings (or /admin/globalSettings.html)Affected if You can access the global settings interface without error
-
Inspect global settings for injected scriptsExamine all fields in the Global Settings page including server name, default timezone, and any custom configurations. Look for unexpected script tags (<script>), event handlers (onload, onclick, onerror), or suspicious JavaScript URLsAffected if Any field contains visible script tags, encoded characters that decode to script content, or unfamiliar scripts that you did not configure
You are affected if your TeamCity version is below 2024.07.3 AND you have access to global settings that may contain injected malicious scripts.
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.07.3
Upgrade TeamCity to version 2024.07.3 or later to receive the vendor patch for stored XSS in global settings. Review existing global settings for any suspicious injected content.
2024.07.3
- Backup your TeamCity data directory and database before upgrading
- Review the official TeamCity upgrade documentation at jetbrains.com
- Download TeamCity version 2024.07.3 or later from the official JetBrains website
- Stop the TeamCity server gracefully
- Install the new version following the standard upgrade procedure
- Start the TeamCity server
- Verify the server global settings are accessible and the upgrade was successful
- Confirm the XSS vulnerability is no longer present by accessing server global settings
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.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 $2,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-47951 — 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-2024-47951 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