CVE-2019-15002 json
An exploitable CSRF vulnerability exists in Atlassian Jira, from versions 7.6.4 to 8.1.0.
published 2025-02-11 20 mo ago modified 2026-06-17 4 mo ago also EUVD-2025-4975
- cvss
- 4.3
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 24%
- public exploits
- 0
- none known
Summary
An exploitable CSRF vulnerability exists in Atlassian Jira, from versions 7.6.4 to 8.1.0. The login form doesn’t require a CSRF token. As a result, an attacker can log a user into the system under an unexpected account.
Patch / fix
- Atlassian Jira Server 8.1.0
- Atlassian Jira Data Center 8.1.0
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 20 mo ago
Exploit prediction
0.32% chance of exploitation in the next 30 days, higher than 24% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CISA ADP | 3.1 | 4.3 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N |
| CNA | 3.1 | 4.3 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N |
Affected products
- Atlassian Jira Server
- Atlassian Jira Data Center
Classification
- Weakness
-
- CWE-352 Cross-Site Request Forgery
References
-
jira.atlassian.com
/browse/JRASERVER-67979
issue-tracking, vendor-advisory
Sources
- CVE List CVE-2019-15002
- NVD CVE-2019-15002
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.