How severe is CVE-2019-11581?

CVE-2019-11581 has a CVSS score of 9.8/10, rated CRITICAL. Immediate patching is strongly recommended.

Which products are affected by CVE-2019-11581?

CVE-2019-11581 affects the following products: atlassian jira server.

How do I patch CVE-2019-11581?

Apply the atlassian jira server security patch or hotfix for CVE-2019-11581 on the affected version, following the vendor advisory for your exact build.

How do I detect CVE-2019-11581 across my infrastructure?

Inventory every atlassian jira server deployment and check each version against the affected-products list above.

How do I mitigate CVE-2019-11581 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands. Alongside that, restrict the management interface to trusted networks and apply the vendor's recommended configuration mitigations.

Is CVE-2019-11581 actively exploited in the wild?

Yes. There are 10 known exploit references for CVE-2019-11581, including 6 in-the-wild exploitations observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2019-11581?

CVE-2019-11581 has an EPSS (Exploit Prediction Scoring System) score of 84.6%, placing it in the 100th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. A score above 50% indicates significantly elevated exploitation risk — immediate patching is strongly recommended.

Is CVE-2019-11581 in the CISA Known Exploited Vulnerabilities catalog?

Yes. CVE-2019-11581 (Atlassian Jira Server and Data Center Server-Side Template Injection Vulnerability) was added to CISA's Known Exploited Vulnerabilities (KEV) catalog on 2022-03-07. CISA required all US federal civilian agencies to remediate this vulnerability by 2022-09-07. The required action was: Apply updates per vendor instructions. Being listed in the KEV catalog is the strongest possible confirmation of active exploitation — treat this as a critical priority.

What type of vulnerability is CVE-2019-11581?

CVE-2019-11581 is classified as CWE-74 (CWE-74). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

Which products and versions are affected by CVE-2019-11581?

CVE-2019-11581 affects atlassian jira server. Check the affected-products list on this page against your deployed version to confirm exposure.

Is there exploit tooling available for CVE-2019-11581?

A Nuclei detection template exists for CVE-2019-11581, meaning automated scanners can fingerprint it. Public exploit tooling significantly increases real-world risk — prioritize patching and ensure detection coverage. Exploit tooling should only ever be used in isolated, authorized testing environments.

When was CVE-2019-11581 published, and has it been updated?

CVE-2019-11581 was published on August 9, 2019 and was last updated on June 17, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🛡️

CISA KEV · ACTIVELY EXPLOITED

CRITICAL severity

CVE-2019-11581 — Jira Server

CRITICAL

CVE-2019-11581 is a critical-severity (CVSS 9.8) CWE-74 vulnerability in atlassian jira server. It is in CISA's Known Exploited Vulnerabilities catalog (added 2022-03-07) — treat it as actively exploited and patch now. A fix is available — see the affected versions and patch details below.

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…

Published

Aug 9, 2019

Updated

Jun 17, 2026

Affected

1 product

Patched

See advisory

Exploits

10 known

Exploitation data as of Oct 22, 2026 · OSV.dev, NVD, CISA KEV, FIRST.org (EPSS)

Exploitation Status

Actively exploited in the wild

Confirmed by CISA's Known Exploited Vulnerabilities catalog on 2022-03-07. Federal agencies were required to remediate by 2022-09-07.
CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
A successful exploit gives an attacker total control of the affected component, not partial access.

Exploitation and automatability from CISA (KEV catalog and SSVC triage) for CVE-2019-11581.

EPSS Exploitation Probability

via FIRST.org ↗

84.6%probability of exploitation in next 30 days

Very High Risk0.00%

Lower risk than most CVEs100th percentile — riskier than 100% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

CVE-2019-11581 by exploitation likelihood (EPSS) against impact (CVSS). In the shaded patch-first corner (EPSS 50%+, CVSS 7.0+).

Where this sits among everything scored

Of 394,803 CVEs with a current EPSS score, this one falls in the 50–90% band (highlighted). Counts from FIRST.org, log-scaled.

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.

Affected Products

1 product · 5 configurations

Application

jira serveratlassian

≥ 8.2.0 && < 8.2.3

range

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.