CVE-2020-7913
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 · uneditedJetBrains YouTrack 2019.2 before 2019.2.59309 was vulnerable to XSS via an issue description.
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 confidenceJetBrains YouTrack 2019.2 before version 59309 contains a cross-site scripting (XSS) vulnerability in the issue description field. The application fails to properly sanitize or encode user-supplied input in issue descriptions, allowing an attacker to inject malicious JavaScript code that executes in the browsers of other users who view the affected issue.
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.0, < 2019.2.59309CVSS 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.
-
Identify YouTrack installation locationLocate the YouTrack installation directory. Common paths include /opt/youtrack, /usr/share/youtrack, or C:\YouTrack on Windows. Check for the youtrack.jar or service configuration files.Affected if YouTrack is installed and running in the environment
-
Determine installed YouTrack versionAccess the YouTrack administration interface and navigate to the About section, typically found under Administration > System > About. Alternatively, check the youtrack.jar file properties or the version displayed in the startup logs.Affected if Unable to retrieve version information
-
Compare version against vulnerable rangeCheck if the installed version falls within the range 2019.2.0 to 2019.2.59308 (inclusive). Versions 2019.2.59309 and later are patched. Compare the numeric build number from the About section against 59309.Affected if Installed version is 2019.2.0 or higher but lower than 2019.2.59309
-
Verify issue description functionality is accessibleConfirm that users can create or edit issues in YouTrack. This vulnerability is exploitable through the issue description field, which accepts user-supplied input.Affected if Issue creation or editing is enabled and users can submit content to description fields
The environment is affected if YouTrack version is 2019.2.0 or higher but below 2019.2.59309, and users have the ability to create or modify issue descriptions where malicious script could be injected.
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 data2019.2.59309
Upgrade YouTrack to version 2019.2.59309 or later to patch the XSS vulnerability in the issue description component. Until upgrade, restrict access to trusted users and monitor for suspicious issue content.
- Consultation3.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 $3,072.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-7913 — 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-2020-7913 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