dbcve.org
JiraApplication · Atlassian

CVE-2020-36236

MEDIUM · 6.1 CVSS v3.1 Published 2021-02-15
Fix available
A fix is available. Upgrade to 8.5.11 / 8.13.3 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
Affected 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 the ViewWorkflowSchemes.jspa and ListWorkflows.jspa endpoints. The affected versions are before version 8.5.11, from version 8.6.0 before 8.13.3, and from version 8.14.0 before 8.15.0.

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

Cross-site scripting (XSS) vulnerability in Atlassian Jira Server and Data Center allows remote attackers to inject arbitrary HTML or JavaScript via the ViewWorkflowSchemes.jspa and ListWorkflows.jspa endpoints. This stored XSS can be exploited to hijack user sessions, steal credentials, or perform actions on behalf of authenticated users.

MitigationUpgrade Jira Server/Data Center to version 8.5.11, 8.13.3, 8.15.0 or later to remediate this 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
Affected:< 8.5.11
Jira Data CenterApplication
Affected:>= 8.6.0, < 8.13.3
Jira ServerApplication
Affected:>= 8.6.0, < 8.13.3>= 8.14.0, < 8.15.0
Jira Software Data CenterApplication
Affected:< 8.5.11>= 8.14.0, < 8.15.0

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. Identify Jira installation version
    Access the Jira administration console and navigate to 'Administration' > 'System' > 'Troubleshooting and support' > 'System Info', or append /rest/api/2/serverInfo to the Jira base URL to retrieve the version number.
    Affected if The displayed version falls within any of these ranges: < 8.5.11, >= 8.6.0 and < 8.13.3, >= 8.14.0 and < 8.15.0. All versions in these ranges are affected.
  2. Verify the workflow schemes endpoint exists
    Navigate to the Jira base URL and append /secure/admin/ViewWorkflowSchemes.jspa. For example: https://your-jira-instance/secure/admin/ViewWorkflowSchemes.jspa. Check if the page loads successfully.
    Affected if The endpoint is accessible and returns a valid HTTP 200 response, indicating the workflow schemes feature is enabled.
  3. Verify the list workflows endpoint exists
    Navigate to the Jira base URL and append /secure/admin/ListWorkflows.jspa. For example: https://your-jira-instance/secure/admin/ListWorkflows.jspa. Check if the page loads successfully.
    Affected if The endpoint is accessible and returns a valid HTTP 200 response, indicating the workflows feature is enabled.
  4. Confirm administrative access to vulnerable endpoints
    Log in to Jira with an account that has administrative or project administrator privileges. Attempt to access both ViewWorkflowSchemes.jspa and ListWorkflows.jspa endpoints to confirm they are reachable by authenticated users.
    Affected if An authenticated user with project or system administration rights can access both endpoints without receiving an access denied error.

Your Jira instance is affected if the installed version falls within the vulnerable ranges AND the workflow schemes or workflows administrative pages are accessible to authenticated users.

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.5.11 / 8.13.3 / 8.15.0 or later
Fixed in 8.5.118.13.38.15.0
Interim mitigation

Upgrade Jira Server/Data Center to version 8.5.11, 8.13.3, 8.15.0 or later to remediate this vulnerability.

Fix this in Jira Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,750
Get the upgrade done

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 locally
dbcve dependency scanner

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