How severe is CVE-2019-20403?

CVE-2019-20403 has a CVSS 3.x base score of 5.3, rated medium severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is low, integrity none, and availability none.

Is CVE-2019-20403 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (71st percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2019-20403?

CVE-2019-20403 primarily affects Atlassian Jira Data Center. In total, 2 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.

How do I fix CVE-2019-20403?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.

When was CVE-2019-20403 published?

CVE-2019-20403 was published on 2020-02-06 and last updated on 2026-06-17.

CVE-2019-20403

CVE-2019-20403 is a medium-severity vulnerability in Atlassian Jira Data Center with a CVSS 3.x base score of 5.3. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low.

Key facts

Severity: Medium (CVSS 3.x base score 5.3)
CVSS v2: 5.0
EPSS exploit prediction: 1% (71st percentile)
Actively exploited: Not listed in CISA KEV
Affected product: Atlassian Jira Data Center
Published: 2020-02-06
Last modified: 2026-06-17

Description

The API in Atlassian Jira Server and Data Center before version 8.6.0 allows remote attackers to determine if a Jira project key exists or not via an information disclosure vulnerability.

Frequently asked questions

What is CVE-2019-20403?: The API in Atlassian Jira Server and Data Center before version 8.6.0 allows remote attackers to determine if a Jira project key exists or not via an information disclosure vulnerability.
How severe is CVE-2019-20403?: CVE-2019-20403 has a CVSS 3.x base score of 5.3, rated medium severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is low, integrity none, and availability none.
Is CVE-2019-20403 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (71st percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2019-20403?: CVE-2019-20403 primarily affects Atlassian Jira Data Center. In total, 2 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2019-20403?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
When was CVE-2019-20403 published?: CVE-2019-20403 was published on 2020-02-06 and last updated on 2026-06-17.

References

https://jira.atlassian.com/browse/JRASERVER-70565

Affected products (2)

cpe:2.3:a:atlassian:jira_data_center:*:*:*:*:*:*:*:*
cpe:2.3:a:atlassian:jira_server:*:*:*:*:*:*:*:*

More vulnerabilities in Atlassian Jira Data Center

CVE-2022-26136 — Critical (CVSS 9.8): A vulnerability in multiple Atlassian products allows a remote, unauthenticated attacker to bypass Servlet Filters used…
CVE-2022-0540 — Critical (CVSS 9.8): A vulnerability in Jira Seraph allows a remote, unauthenticated attacker to bypass authentication by sending a…
CVE-2020-36239 — Critical (CVSS 9.8): Jira Data Center, Jira Core Data Center, Jira Software Data Center from version 6.3.0 before 8.5.16, from 8.6.0 before…
CVE-2025-22157 — High (CVSS 8.8): This High severity PrivEsc (Privilege Escalation) vulnerability was introduced in versions: 9.12.0, 10.3.0, 10.4.0,…
CVE-2024-21683 — High (CVSS 8.8): This High severity RCE (Remote Code Execution) vulnerability was introduced in version 5.2 of Confluence Data Center…
CVE-2022-26137 — High (CVSS 8.8): A vulnerability in multiple Atlassian products allows a remote, unauthenticated attacker to cause additional Servlet…

All CVEs affecting Atlassian Jira Data Center →