dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 7 Sep 2022.
Jira ServerApplication · Atlassian

CVE-2019-11581

CRITICAL · 9.8 CVSS v3.1 Published 2019-08-09
Fix available
A fix is available. Upgrade to 7.6.14 / 7.13.5 or later.
See remediation →
100/100
Remediation priority · Urgent
In the wild High EPSS Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Server-side template injection (SSTI) vulnerability in Jira Server and Data Center's ContactAdministrators and SendBulkMail actions allows remote attackers to inject malicious template code that results in arbitrary code execution on the underlying system.

MitigationUpgrade Jira Server or Data Center to the patched versions (7.6.14, 7.13.5, 8.0.3, 8.1.2, or 8.2.3 or later). Until patched, restrict network access to Jira administration interfaces and consider disabling the affected actions.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Jira ServerApplication
Affected:>= 4.4, < 7.6.14>= 7.7.0, < 7.13.5>= 8.0.0, < 8.0.3>= 8.1.0, < 8.1.2>= 8.2.0, < 8.2.3

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Jira installation version
    Check the Jira footer in the web UI, or access the /about.jspa page while logged in as an administrator, or check the <jira-install>/atlassian-jira/WEB-INF/classes/application-info.xml file if you have file system access
    Affected if Version falls within any of these ranges: >= 4.4 and < 7.6.14; >= 7.7.0 and < 7.13.5; >= 8.0.0 and < 8.0.3; >= 8.1.0 and < 8.1.2; >= 8.2.0 and < 8.2.3
  2. Confirm exposed web access
    Verify that the Jira web interface is accessible over the network. This vulnerability can be exploited remotely if the /secure/ContactAdministrators.jspa or /secure/SendBulkMail.jspa endpoints are reachable without additional authentication beyond normal Jira login
    Affected if The affected endpoints are reachable from a network location where an attacker could send HTTP requests
  3. Verify vulnerable endpoint accessibility
    Attempt to access the ContactAdministrators action by navigating to or sending a request for /secure/ContactAdministrators.jspa. Similarly check /secure/SendBulkMail.jspa. If these pages load or respond, the endpoints are exposed
    Affected if Either endpoint responds and accepts input, indicating the SSTI attack surface is present

You are affected if your Jira Server or Data Center version falls within the vulnerable version ranges AND the ContactAdministrators or SendBulkMail endpoints are accessible to an attacker who can send HTTP requests to your Jira instance.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 7.6.14 / 7.13.5 / 8.0.3 or later
Fixed in 7.6.147.13.58.0.3
Interim mitigation

Upgrade Jira Server or Data Center to the patched versions (7.6.14, 7.13.5, 8.0.3, 8.1.2, or 8.2.3 or later). Until patched, restrict network access to Jira administration interfaces and consider disabling the affected actions.

Recommended fix High confidence

Upgrade to Jira 7.6.14, 7.13.5, 8.0.3, 8.1.2, 8.2.3, or later

  1. 1. Identify the current Jira Server or Data Center version by navigating to Jira Administration > System > System Info or checking the /rest/api/2/serverInfo endpoint
  2. 2. Review the Atlassian upgrade guide and release notes for your target version to understand any breaking changes or required pre-upgrade steps
  3. 3. Perform a full backup of the Jira database and home directory according to Atlassian's documentation
  4. 4. If upgrading across major version ranges (e.g., 7.x to 8.x), set up a staging environment to test applications, plugins, and integrations
  5. 5. Download the appropriate fixed version from Atlassian: 7.6.14, 7.13.5, 8.0.3, 8.1.2, or 8.2.3 (or later)
  6. 6. Stop the Jira service
  7. 7. Follow Atlassian's upgrade instructions to install the new version
  8. 8. Start the Jira service and verify the upgrade was successful
Caveat Upgrading across major version ranges (e.g., 7.x to 8.x) may introduce breaking changes; review Atlassian's upgrade path documentation and test in staging first

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Jira Server Exploited in the wild — priority engagement
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,160
Get it fixed fast

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,656.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-11581 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2019-11581 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data