dbcve.org
UpsourceApplication · Jetbrains

CVE-2019-14961

MEDIUM · 6.1 CVSS v3.1 Published 2019-10-01
Fix available
A fix is available. Upgrade to 2019.1.1412 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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 · unedited
JetBrains Upsource before 2019.1.1412 was not properly escaping HTML tags in a code block comments, leading to 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 · high confidence

JetBrains Upsource before version 2019.1.1412 fails to properly escape HTML tags in code block comments, allowing authenticated users to inject malicious HTML/JavaScript that executes in the browsers of other users viewing those comments (stored XSS).

MitigationUpgrade Upsource to version 2019.1.1412 or later, which implements proper HTML escaping for code block comments to prevent XSS attacks.

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
UpsourceApplication
Affected:< 2019.1.1412

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Locate Upsource installation
    Check common installation directories (e.g., /opt/upsource, C:\Program Files\JetBrains\Upsource, or via systemctl status upsource)
    Affected if Upsource is installed on the system
  2. Identify Upsource version
    Check the version file or admin interface (typically at https://your-upsource-host/about or in <install_dir>/build.txt)
    Affected if Version number is lower than 2019.1.1412
  3. Confirm code review feature is accessible
    Verify that the Upsource web interface is accessible and users can authenticate to access code review and comment functionality
    Affected if Upsource is running and accessible to authenticated users with code review capabilities
  4. Verify comment functionality is in use
    Check if any projects/repositories are configured in Upsource that allow users to post comments on code reviews
    Affected if Users have created or can create code reviews with comments in the Upsource instance

The environment is affected if Upsource is installed with a version lower than 2019.1.1412 and the code review/comment feature is accessible to authenticated users, as the stored XSS in code block comments can be triggered.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to 2019.1.1412 or later
Fixed in 2019.1.1412
Interim mitigation

Upgrade Upsource to version 2019.1.1412 or later, which implements proper HTML escaping for code block comments to prevent XSS attacks.

Fix this in Upsource Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-14961 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2019-14961 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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