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 3 May 2022. Known ransomware use
Confluence ServerApplication · Atlassian

CVE-2019-3396

CRITICAL · 9.8 CVSS v3.1 Published 2019-03-25
Fix available
A fix is available. Upgrade to 6.6.12 / 6.12.3 or later.
See remediation →
100/100
Remediation priority · Urgent
In the wild Ransomware High EPSS Public exploit Remotely reachable No privileges Zero-click Patch available

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
The Widget Connector macro in Atlassian Confluence Server before version 6.6.12 (the fixed version for 6.6.x), from version 6.7.0 before 6.12.3 (the fixed version for 6.12.x), from version 6.13.0 before 6.13.3 (the fixed version for 6.13.x), and from version 6.14.0 before 6.14.2 (the fixed version for 6.14.x), allows remote attackers to achieve path traversal and remote code execution on a Confluence Server or Data Center instance via server-side template injection.

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

CVE-2019-3396 is a critical server-side template injection (SSTI) vulnerability in the Widget Connector macro of Atlassian Confluence Server and Data Center. Attackers can exploit path traversal to achieve remote code execution on the affected server. The vulnerability affects multiple version ranges before the fixed releases (6.6.12, 6.12.3, 6.13.3, and 6.14.2).

MitigationUpgrade Confluence Server/Data Center to one of the specified fixed versions (6.6.12, 6.12.3, 6.13.3, or 6.14.2 or later). As a temporary measure, disable the Widget Connector macro and implement network segmentation or WAF rules to block exploitation attempts.

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
Confluence ServerApplication
Affected:< 6.6.12>= 6.7.0, < 6.12.3>= 6.13.0, < 6.13.3>= 6.14.0, < 6.14.2

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 Confluence Server version
    Access Confluence administrative interface (Administration > General Configuration) or check the confluence-version.properties file in the Confluence home directory
    Affected if The installed version falls into any of these ranges: < 6.6.12; >= 6.7.0 and < 6.12.3; >= 6.13.0 and < 6.13.3; >= 6.14.0 and < 6.14.2
  2. Verify Widget Connector macro status
    Navigate to Confluence Administration > Look and Feel > Macros or check macro configuration files to determine if the Widget Connector macro is enabled
    Affected if The Widget Connector macro is currently enabled (this macro is required for the exploit path)
  3. Inspect template cache for suspicious content
    Check Confluence's template cache or temporary files for unexpected template content, particularly in directories related to the Widget Connector
    Affected if Unrecognized or malicious template code is present in Widget Connector related templates
  4. Review recent access logs for exploit indicators
    Examine Confluence access logs (atlassian-confluence.log) for requests containing '../' path traversal patterns targeting the widget macro endpoint
    Affected if Recent HTTP requests contain path traversal sequences targeting the Widget Connector macro URL pattern

A user is affected if Confluence Server is running a version within the vulnerable ranges AND the Widget Connector macro remains enabled.

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 6.6.12 / 6.12.3 / 6.13.3 or later
Fixed in 6.6.126.12.36.13.3
Vendor patch jira.atlassian.com →
Interim mitigation

Upgrade Confluence Server/Data Center to one of the specified fixed versions (6.6.12, 6.12.3, 6.13.3, or 6.14.2 or later). As a temporary measure, disable the Widget Connector macro and implement network segmentation or WAF rules to block exploitation attempts.

Recommended fix High confidence

Upgrade to 6.6.12 (for 6.5.x and below), 6.12.3 (for 6.7.0-6.12.x), 6.13.3 (for 6.13.x), or 6.14.2 (for 6.14.0-6.14.1)

  1. 1. Take a complete backup of your Confluence Server instance, including the database and home directory.
  2. 2. Identify your current Confluence version from the Administration console.
  3. 3. Determine the appropriate upgrade path based on your current version: For 6.5.x and below, upgrade to 6.6.12; for 6.7.0 through 6.12.x, upgrade to 6.12.3; for 6.13.x, upgrade to 6.13.3; for 6.14.0-6.14.1, upgrade to 6.14.2.
  4. 4. Download the target fixed version from the official Atlassian marketplace or your Atlassian license portal.
  5. 5. Follow Atlassian's standard upgrade documentation for your specific upgrade path.
  6. 6. After upgrade, verify the Widget Connector macro functionality is restored and the vulnerability is patched.
  7. 7. Confirm the new version by checking About Confluence in the Administration console.
Caveat Review Atlassian release notes for your upgrade path as minor version upgrades may include configuration or compatibility changes

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

Fix this in Confluence Server Exploited in the wild — priority engagement
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get it fixed fast

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-3396 — 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-3396 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