CVE-2016-4319 json
Atlassian JIRA Server before 7.1.9 has CSRF in auditing/settings.
published 2017-04-10 9 y ago modified 2026-06-17 4 mo ago also EUVD-2016-5319
- cvss
- 8.8
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.9%
- EPSS 0.9% chance of exploitation in 30 days, percentile 60%
- public exploits
- 0
- none known
Summary
Atlassian JIRA Server before 7.1.9 has CSRF in auditing/settings.
Exploit prediction
0.91% chance of exploitation in the next 30 days, higher than 60% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 8.8 | CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 6.8 | AV:N/AC:M/Au:N/C:P/I:P/A:P |
Affected products
- n/a Atlassian JIRA Server before 7.1.9
Classification
- Weakness
-
- CWE-352 Cross-Site Request Forgery
References
-
securityfocus.com
/bid/97517
vdb-entry, third-party-advisory
- jira.atlassian.com /secure/ReleaseNote.jspa?projectId=10240&version=62034
-
jira.atlassian.com
/browse/JRASERVER-61803
issue-tracking
- confluence.atlassian.com /jiracore/jira-core-7-1-x-release-notes-802161668.html#JIRACore7.1.xreleasenotes-v7.1.9v7.1.9-06July2016
- jira.atlassian.com /browse/JRA-61803
Sources
- CVE List CVE-2016-4319
- NVD CVE-2016-4319
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.