dbcve.org
Jira ServerApplication · Atlassian

CVE-2019-8444

MEDIUM · 5.4 CVSS v3.1 Published 2019-08-23
Fix available
A fix is available. Upgrade to 7.13.6 / 8.3.2 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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 wikirenderer component in Jira before version 7.13.6, and from version 8.0.0 before version 8.3.2 allows remote attackers to inject arbitrary HTML or JavaScript via a cross site scripting (XSS) vulnerability in image attribute specification.

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

The wikirenderer component in Atlassian Jira contains a cross-site scripting (XSS) vulnerability allowing remote attackers to inject arbitrary HTML or JavaScript through image attribute specifications. This stored XSS affects the wiki rendering functionality used in Jira issues, comments, and other text fields.

MitigationUpgrade Jira to version 7.13.6, 8.3.2, or later to patch the vulnerability. Until upgraded, restrict wiki markup input or implement content security policy headers as a compensating control.

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
Jira ServerApplication
Affected:>= 7.7, < 7.13.6>= 8.0.0, < 8.3.2

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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Check Jira Server version
    Log in as administrator, go to Administration > System > Troubleshooting and support tools > System Info, or check the jira-version in <jira-install>/atlassian-jira/WEB-INF/classes/jira-application.properties file
    Affected if The version is 7.7 through 7.13.5, or 8.0.0 through 8.3.1 (meaning it falls within < 7.13.6 or >= 8.0.0 but < 8.3.2)
  2. Confirm wiki renderer is active
    By default Jira uses the wiki renderer for issue descriptions, comments, and custom text fields. Verify in Administration > Issues > Field Configuration that text fields have the Wiki Style Renderer renderer selected
    Affected if Wiki renderer is enabled and used for any user-controllable text fields (issues, comments, descriptions)
  3. Test for XSS via wiki image syntax
    Create or edit an issue/comment and attempt to insert a wiki image with malicious attribute like: !xss.jpg|width=\"1\" onerror=\"alert(1)\"|height=\"1\"! - then save and view the rendered content
    Affected if The rendered output executes JavaScript or reflects unsanitized attribute values in the HTML (indicating the wikirenderer is vulnerable)
  4. Inspect HTTP response for unsanitized output
    Use browser developer tools or a proxy to capture the rendered HTML response when viewing a comment/description containing wiki image markup with custom attributes
    Affected if The HTML response contains unescaped quotes or raw attribute values from the wiki markup (e.g., onerror=, javascript:, or other XSS vectors in image tag attributes)

You are affected if your Jira Server version is 7.7-7.13.5 or 8.0.0-8.3.1 AND the wiki renderer is enabled for user-editable text fields where an attacker can inject crafted image attribute specifications.

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 7.13.6 / 8.3.2 or later
Fixed in 7.13.68.3.2
Interim mitigation

Upgrade Jira to version 7.13.6, 8.3.2, or later to patch the vulnerability. Until upgraded, restrict wiki markup input or implement content security policy headers as a compensating control.

Fix this in Jira Server Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing8.0 h
  • Review / QA4.0 h
20.0 hours of engineering $3,440
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,504.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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