dbcve.org
YoutrackApplication · Jetbrains

CVE-2019-14952

MEDIUM · 6.1 CVSS v3.1 Published 2019-10-01
Fix available
A fix is available. Upgrade to 2019.1.52584 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 YouTrack versions before 2019.1.52584 had a possible XSS in the issue titles.

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

A stored Cross-Site Scripting (XSS) vulnerability in JetBrains YouTrack allows attackers to inject malicious scripts through issue titles. The vulnerability affects versions prior to 2019.1.52584 and requires user interaction (viewing the crafted issue title) to trigger the attack.

MitigationUpgrade YouTrack to version 2019.1.52584 or later. Until then, restrict issue creation/editing permissions to trusted users only and implement Content Security Policy headers.

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
YoutrackApplication
Affected:< 2019.1.52584

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 YouTrack version number
    Access the YouTrack administration area and navigate to the About page (typically /app/about) or check the startup logs in the installation directory for the version string
    Affected if Unable to locate version information for comparison
  2. Compare installed version to vulnerable range
    Review the version number found in the previous step and compare it numerically against 2019.1.52584
    Affected if Installed version is less than 2019.1.52584 (for example, 2019.1.50000 or any 2018.x.x release)
  3. Verify issue functionality is enabled
    Confirm that the YouTrack instance has issue tracking enabled and users can create or view issues through the web interface or API
    Affected if Issue tracking module is disabled or inaccessible to users

Your YouTrack instance is affected if it runs version 2019.1.52584 or earlier and users can view issue titles.

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.52584 or later
Fixed in 2019.1.52584
Interim mitigation

Upgrade YouTrack to version 2019.1.52584 or later. Until then, restrict issue creation/editing permissions to trusted users only and implement Content Security Policy headers.

Fix this in Youtrack Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-14952 — 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-14952 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