JiraApplication · Atlassian
CVE-2019-20414
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 · uneditedAffected versions of Atlassian Jira Server and Data Center allow remote attackers to inject arbitrary HTML or JavaScript via a cross site scripting (XSS) vulnerability in Issue Navigator Basic Search. The affected versions are before version 7.13.9, and from version 8.0.0 before 8.4.2.
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 confidenceThis is a stored cross-site scripting (XSS) vulnerability in Atlassian Jira Server and Data Center's Issue Navigator Basic Search feature. Remote attackers can inject arbitrary HTML or JavaScript code that executes in the context of other users' browsers when they access the affected search functionality.
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
< 7.13.9
Jira Data CenterApplication
>= 8.0.0, < 8.4.2
Jira ServerApplication
>= 8.0.0, < 8.4.2
Jira Software Data CenterApplication
< 7.13.9CVSS 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
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/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.
-
Check Jira versionLog in as an administrator, go to Administration > System > Troubleshooting and support tools > System info. Locate the 'Build number' or 'Version' field. Alternatively, check the footer of any Jira page for the version number.Affected if The installed version is less than 7.13.9, or is 8.0.0 through 8.4.1 (for Data Center/Server variants)
-
Identify Jira deployment typeIn System info or Administration > System > Global Settings, determine if the instance is Jira Server, Jira Data Center, or Jira Software Data Center.Affected if The deployment type matches one of the affected categories (Server, Data Center, or Jira Software Data Center) with a vulnerable version
-
Verify Basic Search is accessibleNavigate to the Issue Navigator (Issues > Search for Issues). Confirm that Basic Search mode is available and users can access it.Affected if Basic Search functionality is enabled and users have permission to use it
-
Check for saved filters using Basic SearchGo to Issues > Search for Issues > Basic Search. Look for any saved filters or recent searches that may contain user-supplied content in search fields (such as project names, issue types, or custom field values).Affected if There are saved filters containing potentially malicious user-supplied content in search fields
A user is affected if their Jira installation matches one of the listed version ranges AND the Basic Search feature is accessible to users who could have injected malicious script content.
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 data7.13.98.4.2
Upgrade Jira to version 7.13.9, 8.4.2, or later to resolve the vulnerability. Prior to upgrading, ensure proper backups and test the upgrade in a non-production environment.
Fix this in Jira
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,656.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-20414 — 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-20414 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