How severe is CVE-2020-36289?

CVE-2020-36289 has a CVSS score of 5.3/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2020-36289?

Affected package information for CVE-2020-36289 is not yet fully mapped. Check the official advisory links for details.

How do I fix CVE-2020-36289?

No fixed version has been published for CVE-2020-36289 yet. Monitor the advisory for updates, apply mitigations recommended by the vendor, and use O3 Security to track when a fix becomes available in your stack.

Is CVE-2020-36289 actively exploited in the wild?

No public exploit code has been indexed for CVE-2020-36289 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2020-36289?

CVE-2020-36289 has an EPSS (Exploit Prediction Scoring System) score of 92.0%, placing it in the 100th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. A score above 50% indicates significantly elevated exploitation risk — immediate patching is strongly recommended.

What type of vulnerability is CVE-2020-36289?

CVE-2020-36289 is classified as CWE-863 (CWE-863). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

Which products and versions are affected by CVE-2020-36289?

CVE-2020-36289 affects atlassian data center; atlassian jira; atlassian jira data center; atlassian jira server. Check the affected-products list on this page against your deployed version to confirm exposure.

Is there exploit tooling available for CVE-2020-36289?

A Nuclei detection template exists for CVE-2020-36289, meaning automated scanners can fingerprint it. Public exploit tooling significantly increases real-world risk — prioritize patching and ensure detection coverage. Exploit tooling should only ever be used in isolated, authorized testing environments.

When was CVE-2020-36289 published, and has it been updated?

CVE-2020-36289 was published on May 12, 2021 and was last updated on November 21, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

CVE-2020-36289: Data Center CWE-863 (Medium 5.3)

EPSS Exploitation Probability

via FIRST.org ↗

92.0%probability of exploitation in next 30 days

Very High Risk100th percentile0.00%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Description

Affected versions of Atlassian Jira Server and Data Center allow an unauthenticated user to enumerate users via an Information Disclosure vulnerability in the QueryComponentRendererValue!Default.jspa endpoint. The affected versions are before version 8.5.13, from version 8.6.0 before 8.13.5, and from version 8.14.0 before 8.15.1.

Affected Products

4 products · 6 configurations

Application

data centeratlassian

< 8.5.13

range

Application

jiraatlassian

< 8.5.13

range

Application

jira data centeratlassian

≥ 8.14.0 && < 8.15.1

range

Application

jira serveratlassian

≥ 8.14.0 && < 8.15.1

range

Frequently Asked Questions

Affected versions of Atlassian Jira Server and Data Center allow an unauthenticated user to enumerate users via an Information Disclosure vulnerability in the QueryComponentRendererValue!Default.jspa endpoint. The affected versions are before version 8.5.13, from version 8.6.0 before 8.13.5, and from version 8.14.0 before 8.15.1.

O3 Security · Impact-Aware SCA

Is CVE-2020-36289 in your stack?

O3 detects CVE-2020-36289 across dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my stack How O3 SCA works