dbcve.org
JiraApplication · Atlassian

CVE-2020-14169

MEDIUM · 6.1 CVSS v3.1 Published 2020-07-01
Fix available
A fix is available. Upgrade to 8.9.1 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
The quick search component in Atlassian Jira Server and Data Center before 8.9.1 allows remote attackers to inject arbitrary HTML or JavaScript via a Cross-Site Scripting (XSS) vulnerability

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

This is a stored Cross-Site Scripting (XSS) vulnerability in the quick search component of Atlassian Jira Server and Data Center. Remote attackers can inject arbitrary HTML or JavaScript that gets executed when other users interact with the quick search feature.

MitigationUpgrade Jira Server or Data Center to version 8.9.1 or later to patch the XSS vulnerability in the quick search component.

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
Affected:< 8.9.1
Jira Software Data CenterApplication
Affected:< 8.9.1

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. Confirm Jira is running
    Access the application login page or administration console and verify the Atlassian Jira interface is present
    Affected if Jira Server or Data Center is deployed in the environment
  2. Identify the installed Jira version
    Navigate to the administration panel: Administration > System > Troubleshooting and support tools > System Info, or append /secure/AdminHello.jspa to the base URL
    Affected if The displayed version number is less than 8.9.1 (for example, 8.9.0, 8.8.x, 8.7.x, etc.)
  3. Check if quick search is accessible
    Locate the quick search input field typically found in the Jira header/navigation bar, or access it via the keyboard shortcut (g then g)
    Affected if The quick search feature is available to users in the Jira interface
  4. Verify Data Center vs Server
    In the administration panel, check System > System Info or look for clustering/multi-node indicators; Data Center typically shows a license type of 'Jira Software Data Center'
    Affected if The instance is Jira Software Data Center and version is below 8.9.1

If Jira Server or Data Center is running version 8.9.1 or later, the environment is not affected by this stored XSS in quick search.

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 8.9.1 or later
Fixed in 8.9.1
Interim mitigation

Upgrade Jira Server or Data Center to version 8.9.1 or later to patch the XSS vulnerability in the quick search component.

Fix this in Jira Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,560
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,096.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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