CVE-2019-11581
CVE-2019-11581 is a security flaw in Atlassian Jira Server and Data Center, a wiki companies use for internal documents. Attackers can run their own code on Atlassian Jira Server and Data Center. The US Cybersecurity and Infrastructure Security Agency (CISA) added it to its catalog of flaws known to be used in attacks on 7 Mar 2022.[1]
Atlassian Jira Server and Data Center is business software or equipment. Most families won’t have it, but attackers break into it to get inside companies, and from there to what those companies hold about their customers, patients and staff. Fixed in version unspecified, 7.6.14, 7.13.5 and 8.0.3 and others of Jira Server and Data Center.
Description
CISA calls it a server-side template injection in Atlassian Jira Server and Data Center. In its words: “Atlassian Jira Server and Data Center contain a server-side template injection vulnerability which can allow for remote code execution.”[1]
The CVE record adds: “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.”[2]
The underlying weakness is CWE-74, in MITRE’s list of common software weaknesses.
It scores 9.8 out of 10 on the Common Vulnerability Scoring System, which rates it critical, scored by NVD using CVSS 3.1.[2]
Affected versions
NVD’s record lists these fixed versions: in each line, everything before the version shown is affected.[2]
| Product | Fixed in |
|---|---|
| Jira Server and Data Center | unspecified |
| Jira Server and Data Center | 7.6.14 |
| Jira Server and Data Center | 7.13.5 |
| Jira Server and Data Center | 8.0.3 |
| Jira Server and Data Center | 8.1.2 |
| Jira Server and Data Center | 8.2.3 |
Most families won’t have Atlassian Jira Server and Data Center; it’s for whoever looks after IT at work.
Exploitation
CISA added it to its catalog of known exploited vulnerabilities on 7 Mar 2022, 941 days after it was made public. CISA lists a flaw only when it has reliable evidence of it being exploited, and gave US federal agencies until 7 Sep 2022 to fix it.[1]
FIRST’s Exploit Prediction Scoring System, which estimates how likely a flaw is to be used in attacks in the next 30 days from what it sees across the internet, puts it at 85%. That’s in the top 1% of the flaws it scores.[4]
CISA assesses it as automatable: attackers can run it against many targets at once.
CISA doesn’t say who was attacked, or how.
Fix
Atlassian has published a fix or advice.[3] CISA’s required action: “Apply updates per vendor instructions.”[1]
- Check whether you use it.Atlassian Jira Server and Data Center is business software or equipment, so most families won’t have it. If you run a business, or work from home on company equipment, ask whoever looks after your IT.
- Send this page to your IT person.Ask them to confirm it’s fixed (fixed in version unspecified, 7.6.14, 7.13.5 and 8.0.3 and others of Jira Server and Data Center), or not in use. CISA gave US government agencies until 7 Sep 2022 to fix it.
- If it can’t be fixed, take it offline.CISA’s advice when there’s no fix is to stop using the product, or take it off the internet, until there is one.
You can’t fix someone else’s server, but you can watch for what follows a break-in like this: a breach notice, a password reset you didn’t ask for, or a scam message that knows things it shouldn’t. HARD watches for those for you and your family.
Timeline
| Date | Event |
|---|---|
| The flaw is made public in the National Vulnerability Database, with a severity score of 9.8.[2] | |
| CISA adds it to its catalog of flaws known to be used in attacks.[1] | |
| CISA’s deadline for US government agencies to fix it.[1] | |
| FIRST puts the odds of it being used in attacks in the next 30 days at 85%.[4] |
See also
Other Atlassian Jira Server and Data Center flaws
- CVE-2021-26086: path traversal ·
Other Atlassian flaws
- CVE-2026-21589, Atlassian products: files or directories accessible to external parties ·
- CVE-2023-22527, Atlassian Confluence Data Center and Server: template injection ·
- CVE-2023-22518, Atlassian Confluence Data Center and Server: improper authorization ·
- CVE-2023-22515, Atlassian Confluence Data Center and Server: broken access control ·
- CVE-2022-36804, Atlassian Bitbucket Server and Data Center: command injection ·
Similar flaws
- CVE-2025-20337, Cisco Identity Services Engine: injection ·
- CVE-2025-20281, Cisco Identity Services Engine: injection ·
- CVE-2022-43769, Hitachi Vantara Pentaho Business Analytics (BA) Server: pentaho BA server special element injection ·
- CVE-2022-35914, Teclib GLPI: remote code execution ·
- CVE-2022-46169, Cacti: command injection ·
Added the same day
- CVE-2022-26486, Mozilla Firefox: use-after-free ·
- CVE-2022-26485, Mozilla Firefox: use-after-free ·
- CVE-2021-21973, VMware vCenter Server and Cloud Foundation: server side request forgery (SSRF) ·
- CVE-2020-8218, Pulse Secure Pulse Connect Secure: code injection ·
- CVE-2017-6077, NETGEAR Wireless Router DGN2200: dGN2200 remote code execution ·
Every Atlassian flaw on CISA’s list · Everything added in March 2022
References
- ^ Cybersecurity and Infrastructure Security Agency. “Atlassian Jira Server and Data Center Server-Side Template Injection Vulnerability”. Known Exploited Vulnerabilities Catalog, added 7 Mar 2022.
- ^ National Institute of Standards and Technology. “CVE-2019-11581 Detail”. National Vulnerability Database, published 9 Aug 2019.
- ^ Atlassian. Advisories and fixes: jira.atlassian.com.
- ^ FIRST. “Exploit Prediction Scoring System”. EPSS 0.846, percentile 99.7, 31 Oct 2026.
- CVE Program. “CVE-2019-11581”. The official CVE record.
This article is built from CISA’s catalog (version 2026.10.30), NVD’s record and FIRST’s scores, kept in HARD’s database and checked every morning. The plain English is HARD’s.