# CVE-2019-11581: Atlassian Jira Server and Data Center Server-Side Template Injection

> Remote attackers can execute arbitrary code on Jira Server or Data Center via server-side template injection in mail actions.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Yes, since 7 Mar 2022 (CISA KEV)
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Aug 2019
- **Updated:** 21 Oct 2025
- **Also known as:** GHSA-55hv-x43w-phcv

## What is CVE-2019-11581?

CVE-2019-11581 is a critical code injection vulnerability in Atlassian Jira Server, published on 9 Aug 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

There was a server-side template injection vulnerability in Jira Server and Data Center, in the ContactAdministrators and the SendBulkMail actions. An attacker is able to remotely execute code on systems that run a vulnerable version of Jira Server or Data Center. All versions of Jira Server and Data Center from 4.4.0 before 7.6.14, from 7.7.0 before 7.13.5, from 8.0.0 before 8.0.3, from 8.1.0 before 8.1.2, and from 8.2.0 before 8.2.3 are affected by this vulnerability.

Weakness: CWE-74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component)

## Which versions are affected by CVE-2019-11581?

It affects 1 product.


Products: Atlassian Jira Server.

## How do I fix CVE-2019-11581?

No fix has been published for CVE-2019-11581 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 7 Sep 2022.

## Is CVE-2019-11581 being exploited?

Yes. Attackers have exploited CVE-2019-11581 in the wild since at least 7 Mar 2022.

Public exploit code:

- Atlassian JIRA Template injection vulnerability RCE (github_poc): https://github.com/jas502n/CVE-2019-11581
- CVE-2019–11581 PoC (github_poc): https://github.com/kobs0N/CVE-2019-11581
- Atlassian Jira unauthen template injection (github_poc): https://github.com/PetrusViet/CVE-2019-11581
- Atlassian Jira Server-Side Template Injection (nuclei): http/cves/2019/CVE-2019-11581.yaml

## Other vulnerabilities in Atlassian Jira Server

- [CVE-2019-20400](https://insights.sbomify.com/CVE-2019-20400/): Code injection in Jira Server (high 7.8)
- [CVE-2020-14177](https://insights.sbomify.com/CVE-2020-14177/): Denial of service in Jira Server (medium 6.5)
- [CVE-2019-20401](https://insights.sbomify.com/CVE-2019-20401/): Cross-site request forgery in Jira Server (medium 6.5)
- [CVE-2019-14998](https://insights.sbomify.com/CVE-2019-14998/): Cross-site request forgery in Jira (medium 6.5)
- [CVE-2019-8451](https://insights.sbomify.com/CVE-2019-8451/): Server-side request forgery in Jira (medium 6.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-11581 and fix it if it is affected.

What it is: CVE-2019-11581 is a critical code injection vulnerability in Atlassian Jira Server, published on 9 Aug 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2019-11581 in the wild since at least 7 Mar 2022.

Affected product: Atlassian Jira Server. 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-2019-11581/ (Markdown: https://insights.sbomify.com/CVE-2019-11581/index.md)
```

## Sources

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

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