CVE-2019-16171
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 YouTrack through 2019.2.56594, stored XSS was found on the issue page.
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 confidenceStored cross-site scripting (XSS) vulnerability in JetBrains YouTrack allows attackers to inject malicious JavaScript code into issue pages. The payload is permanently stored on the server and executes when other users view the affected issue, potentially enabling session hijacking, credential theft, or unauthorized actions.
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<= 2019.2.56594CVSS 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.
-
Confirm YouTrack installationIdentify if JetBrains YouTrack is installed in your environment. This may be running as a service, installed via installer, or deployed in a container. Check for YouTrack processes or installation directories.Affected if YouTrack is present in the environment
-
Check YouTrack versionLocate the installed YouTrack version number. This is typically accessible through the YouTrack web interface by navigating to the 'About' or 'Administration > System' section, or by checking installation logs and system information.Affected if The installed version is 2019.2.56594 or any earlier version (version number is less than or equal to 2019.2.56594)
-
Verify issue functionality is accessibleConfirm that the issue tracking module is active and users can create, view, or edit issues. The XSS vulnerability resides in issue page fields where malicious code can be stored.Affected if Issue pages and their input fields are accessible to users (this is required for the XSS to be exploitable)
-
Inspect stored issue contentReview existing issues in the system for any suspicious script tags, JavaScript event handlers, or encoded payloads in issue titles, descriptions, or custom fields. Check issue data in the database or through the YouTrack interface.Affected if Any issue contains unsanitized user-supplied script content that could execute in other users' browsers
You are affected if YouTrack version is 2019.2.56594 or earlier and issue pages with user-controllable fields are accessible in your environment.
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.
From vendor dataUpgrade YouTrack to version 2019.2.56595 or later. If immediate patching is not possible, implement output encoding and input validation on issue page fields as a compensating control.
- Consultation2.0 h
- Implementation4.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 $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-16171 — 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-2019-16171 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