How severe is CVE-2019-3399?

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

Is CVE-2019-3399 being actively exploited?

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

What products are affected by CVE-2019-3399?

CVE-2019-3399 primarily affects Atlassian Jira. 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-3399?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.

When was CVE-2019-3399 published?

CVE-2019-3399 was published on 2019-04-30 and last updated on 2026-06-17.

CVE-2019-3399

CVE-2019-3399 is a high-severity vulnerability in Atlassian Jira with a CVSS 3.x base score of 7.5. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-862.

Key facts

Severity: High (CVSS 3.x base score 7.5)
CVSS v2: 5.0
EPSS exploit prediction: 2% (79th percentile)
Actively exploited: Not listed in CISA KEV
Weakness: CWE-862
Affected product: Atlassian Jira
Published: 2019-04-30
Last modified: 2026-06-17

Description

The BrowseProjects.jspa resource in Jira before version 7.13.2, and from version 8.0.0 before version 8.0.2 allows remote attackers to see information for archived projects through a missing authorisation check.

Frequently asked questions

What is CVE-2019-3399?: The BrowseProjects.jspa resource in Jira before version 7.13.2, and from version 8.0.0 before version 8.0.2 allows remote attackers to see information for archived projects through a missing authorisation check.
How severe is CVE-2019-3399?: CVE-2019-3399 has a CVSS 3.x base score of 7.5, rated high severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity none, and availability none.
Is CVE-2019-3399 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 2% (79th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2019-3399?: CVE-2019-3399 primarily affects Atlassian Jira. 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-3399?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
When was CVE-2019-3399 published?: CVE-2019-3399 was published on 2019-04-30 and last updated on 2026-06-17.

References

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

Affected products (2)

cpe:2.3:a:atlassian:jira:*:*:*:*:*:*:*:*
cpe:2.3:a:atlassian:jira_server:*:*:*:*:*:*:*:*

More vulnerabilities in Atlassian Jira

CVE-2020-14172 — Critical (CVSS 9.8): This issue exists to document that a security improvement in the way that Jira Server and Data Center use velocity…
CVE-2019-20409 — Critical (CVSS 9.8): The way in which velocity templates were used in Atlassian Jira Server and Data Center prior to version 8.8.0 allowed…
CVE-2017-5983 — Critical (CVSS 9.8): The JIRA Workflow Designer Plugin in Atlassian JIRA Server before 6.3.0 improperly uses an XML parser and deserializer,…
CVE-2012-2926 — Critical (CVSS 9.1): Atlassian JIRA before 5.0.1; Confluence before 3.5.16, 4.0 before 4.0.7, and 4.1 before 4.1.10; FishEye and Crucible…
CVE-2010-1165 — Critical (CVSS 9.0): Atlassian JIRA 3.12 through 4.1 allows remote authenticated administrators to execute arbitrary code by modifying the…
CVE-2017-18113 — High (CVSS 8.8): The DefaultOSWorkflowConfigurator class in Jira Server and Jira Data Center before version 8.18.1 allows remote…

All CVEs affecting Atlassian Jira →

Other CWE-862 (Missing Authorization) vulnerabilities

CVE-2026-0092 — Critical (CVSS 10.0): In Package Manager, there is a possible device lock controller bypass due to a missing permission check. This could…
CVE-2026-33712 — Critical (CVSS 10.0): Typebot is a chatbot builder tool. In versions 3.15.2 and prior, the preview chat endpoint (POST…
CVE-2026-2031 — Critical (CVSS 10.0): An Improper Access Control vulnerability in several internal API endpoints for Google Cloud Application Integration…
CVE-2026-34976 — Critical (CVSS 10.0): Dgraph is an open source distributed GraphQL database. Prior to 25.3.1, the restoreTenant admin mutation is missing…
CVE-2025-30416 — Critical (CVSS 10.0): Sensitive data disclosure and manipulation due to missing authorization. The following products are affected: Acronis…
CVE-2025-45854 — Critical (CVSS 10.0): /server/executeExec of JEHC-BPM 2.0.1 allows attackers to execute arbitrary code via execParams.

Browse all CWE-862 (Missing Authorization) vulnerabilities →