LiveActive security incident?Get immediate response
CVE Record

CVE-2021-31908: In JetBrains TeamCity before 2020.2.3, stored XSS was possible on several pages.

In JetBrains TeamCity before 2020.2.3, stored XSS was possible on several pages.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2021-31908 is a stored cross-site scripting issue in JetBrains TeamCity before 2020.2.3. Stored XSS means malicious content could persist in the application and run when another user views affected pages. In a CI/CD system, this can matter because TeamCity often handles build access, developer workflows, and sensitive operational context.

Executive priority

Schedule remediation in the normal security patch cycle, sooner for internet-exposed or broadly shared TeamCity instances. The business concern is not service outage; it is potential compromise of trusted CI/CD users through stored content.

Technical view

The public record states that JetBrains TeamCity versions before 2020.2.3 allowed stored XSS on several pages. The source bundle does not provide CVSS, CWE, affected page names, prerequisites, or exploit details. Treat exposure as version-driven: TeamCity below 2020.2.3 is potentially affected.

Likely exposure

Organizations running JetBrains TeamCity before 2020.2.3 are the stated exposure group. Risk is higher where many users can add content viewed by administrators or other privileged TeamCity users.

Exploitation context

The provided sources do not show active exploitation, and the CVE is not listed as KEV in the bundle. Stored XSS still warrants attention because successful abuse may affect users who view stored content inside TeamCity.

Researcher notes

Evidence is sparse: no CVSS, CWE, affected pages, or exploit prerequisites are included. Do not infer unauthenticated reachability or active exploitation. Focus validation on version, exposure surface, user privilege boundaries, and whether untrusted users can store content viewed by privileged users.

Mitigation direction

  • Upgrade TeamCity to 2020.2.3 or later.
  • Review JetBrains guidance for any newer recommendations.
  • Restrict TeamCity access to trusted users and networks.
  • Limit permissions for users who can create visible content.
  • Investigate suspicious TeamCity activity before rotating credentials.

Validation and detection

  • Inventory all TeamCity instances and their versions.
  • Confirm no production instance runs below 2020.2.3.
  • Check whether TeamCity is internet-accessible.
  • Review TeamCity user roles and content creation permissions.
  • Review logs for unusual account or project changes.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2021-31908 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.