Threats / Atlassian / CVE-2019-11581
CVE-2019-11581
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-06-22
Atlassian Jira Server and Data Center vulnerability
Atlassian Jira Server and Data Center are vulnerable to server-side template injection, enabling remote code execution on affected instances.
Verdict
Today item — known-exploited.
A server-side template injection flaw in Jira Server and Data Center allows unauthenticated or low-privileged attackers to execute arbitrary code on the server. The vulnerability has been actively exploited in the wild with high EPSS score.
01
Is it exploitable?
— the evidence, ranked above the scoreExploit available
Fully weaponized — public exploit code is cataloged for this vulnerability.We link the existence of the exploit; we do not host or redistribute payloads.
Reported exploitation
781 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2022-03-07).
Probability (EPSS)
EPSS 0.84621 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
Affected: Atlassian, Jira Server and Data Center. Confirm exact fixed builds in the vendor advisory.
Weakness (CWE)
Mapped to CWE-74 CWE-74 — weakness family: Injection.CWE assignment from the public NVD record; the weakness class drives how the flaw is exploited.
02
Who’s exploiting it?
— attribution turns risk into urgencyAttribution not established
No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.
03
Why it matters
— the attack path, told twice: adversary, then board1
Front door — unauthenticated access narrative 1
Attacker
I craft a malicious template payload and submit it through a Jira input field that processes server-side templates without proper sanitization.
Business
Attackers gain code execution capability on the Jira server, leading to potential data theft, service disruption, or lateral movement within the network.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I execute arbitrary commands on the compromised Jira instance to establish persistence or escalate privileges within the environment.
Business
The organization loses control of its issue tracking system and faces potential compromise of sensitive project data, credentials, and integrated systems.
04
What to do
— defensible action- Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05