Security readout for executives and security teams
Plain-English summary
This CVE affects Jira Server and Jira Data Center issue navigation/search pages. A remote attacker could inject HTML or JavaScript through DOM XSS caused by parameter pollution. Impact depends on user interaction and Jira exposure, but successful XSS can compromise sessions or trusted browser actions.
Executive priority
Treat as a prompt patching item for affected Jira systems, not an emergency based on current evidence. Raise priority for externally reachable Jira or environments with sensitive project data.
Technical view
CVE-2020-36288 is a DOM cross-site scripting issue in Jira Server and Data Center issue navigation/search view. Affected ranges are before 8.5.12, 8.6.0 before 8.13.4, and 8.14.0 before 8.15.1. The source attributes the flaw to parameter pollution.
Likely exposure
Organizations running Atlassian Jira Server or Jira Data Center in the listed affected version ranges are potentially exposed, especially where Jira is reachable by broad internal or external user populations.
Exploitation context
The provided sources describe remote attacker capability but do not show active exploitation. The CVE is not listed as CISA KEV in the supplied bundle. No exploit status beyond the vulnerability description is evidenced here.
Researcher notes
Evidence is limited to CVE and Atlassian references. No CVSS, CWE, proof-of-concept status, or confirmed exploitation is supplied. Avoid assuming broader Atlassian products are affected.
Mitigation direction
- Upgrade Jira Server/Data Center to 8.5.12, 8.13.4, 8.15.1, or later applicable versions.
- Review Atlassian JRASERVER-72115 for vendor guidance and fixed-version details.
- Prioritize internet-facing or broadly accessible Jira instances first.
- If upgrade timing is uncertain, track vendor-recommended compensating controls.
Validation and detection
- Inventory Jira Server and Jira Data Center versions across all environments.
- Flag instances before 8.5.12, 8.6.0-8.13.3, and 8.14.0-8.15.0.
- Confirm upgraded systems report a fixed or later version.
- Record remediation status against CVE-2020-36288 and JRASERVER-72115.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CVE-2020-36288 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://jira.atlassian.com/browse/JRASERVER-72115CVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.