JiraApplication · Atlassian
CVE-2020-14164
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 · uneditedThe WYSIWYG editor resource in Jira Server and Data Center before version 8.8.2 allows remote attackers to inject arbitrary HTML or JavaScript names via an Cross Site Scripting (XSS) vulnerability by pasting javascript code into the editor field.
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 confidenceThe WYSIWYG editor in Jira Server and Data Center before version 8.8.2 does not properly sanitize user input, allowing remote attackers to inject arbitrary HTML or JavaScript by pasting malicious code into the editor field. This is a stored Cross-Site Scripting (XSS) vulnerability.
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
JiraApplication
< 8.8.2
Jira Software Data CenterApplication
< 8.8.2CVSS 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.
-
Locate Jira installation directoryFind the Jira home directory (JIRA_HOME) and installation directory (JIRA_INSTALL). The installation typically contains atlassian-jira directory with VERSION file in the bin folder.Affected if Cannot determine version without locating installation
-
Check installed Jira versionLook for the VERSION file in the Jira installation directory (typically atlassian-jira/WEB-INF/classes or in the bin folder). Alternatively, access Jira administration > System > System Info to view the version number.Affected if Version is displayed as a number that can be compared to 8.8.2
-
Verify Data Center vs ServerCheck the license type in Jira administration or examine the installation for Data Center specific components (cluster.properties, ha directories, or Data Center license). Server installations have a single node.Affected if Product type is Jira Server or Jira Software Server (not Data Center) but still affects both if version < 8.8.2
-
Compare version to affected rangeIf version is found, compare: any version below 8.8.2 (e.g., 8.8.1, 8.7.3, 8.6.0, 8.5.0, earlier 8.x versions, or 7.x versions) is affected. Versions 8.8.2 and later are not affected.Affected if Installed version is less than 8.8.2 for either Jira Server or Jira Software Data Center
A Jira Server or Jira Software Data Center installation with a version number below 8.8.2 is vulnerable to stored XSS in the WYSIWYG editor.
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 data8.8.2
Upgrade Jira Server or Data Center to version 8.8.2 or later to remediate this vulnerability.
Fix this in Jira
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-14164 — 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-14164 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