# CVE-2016-4319: Cross-site request forgery in Atlassian JIRA Server before 7.1.9

> Cross-site request forgery in Atlassian JIRA Server allows attackers to modify auditing settings via crafted requests.

- **Severity:** High 8.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 10 Apr 2017
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-r798-mxm8-76rv

## What is CVE-2016-4319?

CVE-2016-4319 is a high-severity vulnerability in Atlassian Jira, published on 10 Apr 2017. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Atlassian JIRA Server before 7.1.9 has CSRF in auditing/settings.

Weakness: CWE-352 (Cross-Site Request Forgery)

## Which versions are affected by CVE-2016-4319?

It affects 1 product.


Products: Atlassian Jira.

## How do I fix CVE-2016-4319?

No fix has been published for CVE-2016-4319 yet. Limit exposure of the affected software until one is available.

## Is CVE-2016-4319 being exploited?

There is no known exploitation of CVE-2016-4319 in the wild and no public exploit code.

## Other vulnerabilities in Atlassian Jira

- [CVE-2020-14172](https://insights.sbomify.com/CVE-2020-14172/): Deserialization in Jira Server (critical 9.8)
- [CVE-2019-20409](https://insights.sbomify.com/CVE-2019-20409/): Code injection in Jira Server (critical 9.8)
- [CVE-2017-5983](https://insights.sbomify.com/CVE-2017-5983/): Deserialization in n/a (critical 9.8)
- [CVE-2010-1165](https://insights.sbomify.com/CVE-2010-1165/): Code injection in n/a (critical 9.0)
- [CVE-2019-8443](https://insights.sbomify.com/CVE-2019-8443/): Auth bypass in Jira (high 8.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2016-4319 and fix it if it is affected.

What it is: CVE-2016-4319 is a high-severity vulnerability in Atlassian Jira, published on 10 Apr 2017. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2016-4319 in the wild and no public exploit code.

Affected product: Atlassian Jira. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2016-4319/ (Markdown: https://insights.sbomify.com/CVE-2016-4319/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2016-4319
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2016-4319
- OSV: https://osv.dev/vulnerability/CVE-2016-4319

---
From sbomify Insights: https://insights.sbomify.com/CVE-2016-4319/
Summaries are generated and may contain mistakes; the official description above is the record.