CVE-2019-3398 — Atlassian Confluence Server and Data Center Path Traversal Vulnerability
Confluence Server and Data Center had a path traversal vulnerability in the downloadallattachments resource. A remote attacker who has permission to add attachments to pages and / or blogs or to create a new space or a personal space or who has 'Admin' permissions for a space can exploit this path traversal vulnerability to write files to arbitrary locations which can lead to remote code execution on systems that run a vulnerable version of Confluence Server or Data Center. All versions of Confluence Server from 2.0.0 before 6.6.13 (the fixed version for 6.6.x), from 6.7.0 before 6.12.4 (the fixed version for 6.12.x), from 6.13.0 before 6.13.4 (the fixed version for 6.13.x), from 6.14.0 before 6.14.3 (the fixed version for 6.14.x), and from 6.15.0 before 6.15.2 are affected by this vulnerability.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- Confirmed exploitation (CISA KEV)+35
- Public exploit/PoC (nuclei, exploitdb, github)+18
- EPSS 97% (30-day exploitation probability)+15
- Technical severity (high)+6
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
CISA SSVC assessment CISA
Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
- Documented patch — jira.atlassian.com (NIST National Vulnerability Database)
CISA required action CISA
Apply updates per vendor instructions.
US federal deadline: May 3, 2022 — passed 1628 day(s) ago
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Atlassian Confluence, Atlassian Confluence Server).
- Treat as emergency remediation: the CVE is in CISA KEV (confirmed exploitation).
- Apply the fixed version or the patch documented under Remediation.
- EPSS ahead of 100% of scored CVEs: prioritize it in the patch queue.
- Search available logs for exploit probes matching the vulnerability class (file handling), errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Atlassian | Confluence |
≥ 2.0.0 and < unspecified< 6.6.13≥ 6.7.0 and < unspecified< 6.12.4≥ 6.13.0 and < unspecified< 6.13.4≥ 6.14.0 and < unspecified< 6.14.3 and 2 more≥ 6.15.0 and < unspecified< 6.15.2 |
Vulnerable | CVE Program (cve.org) e CISA ADP |
| Atlassian | Confluence Server | ≥ 2.0 and < 6.6.13≥ 6.7.0 and < 6.12.4≥ 6.13.0 and < 6.13.4≥ 6.14.0 and < 6.14.3≥ 6.15.0 and < 6.15.2 | Vulnerable | NIST National Vulnerability Database |
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Every base score collected
Sources score independently and may disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Scored by |
|---|---|---|---|---|---|
| 8.8 | CVSS 3.1 | High | 2.8 | 5.9 | nvd@nist.gov via NIST National Vulnerability Database |
| 8.8 | CVSS 3.1 | High | 2.8 | 5.9 | 134c704f-9b21-4f2e-91b3-4a467353bcc0 via NIST National Vulnerability Database |
| 8.8 | CVSS 3.1 | High | — | — | GitHub, Inc. via GitHub Security Advisories |
| 8.8 | CVSS 3.1 | High | — | — | CISA-ADP via CVE Program (cve.org) e CISA ADP |
| 9.0 | CVSS 2.0 | High | 8.0 | 10.0 | nvd@nist.gov via NIST National Vulnerability Database |
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H (score shown at the top: nvd@nist.gov) Weakness MITRE
Weakness class according to MITRE’s CWE catalog.
CISA KEV details CISA
CISA lists a CVE once it has evidence of exploitation against real targets.
CISA records ransomware use only for campaigns it has confirmed, so “Unknown” means unrecorded, not ruled out. The deadline binds US federal agencies; for everyone else it is a reference date.
Public exploits, PoCs and detection templates
Public code that demonstrates or tests the flaw raises the odds of mass exploitation — and Nuclei templates help find vulnerable assets in your environment.
- Atlassian Confluence 6.15.1 - Directory Traversal Nov 12, 2019
- Python script to exploit confluence path traversal vulnerability cve-2019-3398 ★ 15 Apr 20, 2019
- 132231g/CVE-2019-3398 ★ 0 Jan 28, 2024
Warning: public PoCs are sometimes disguised malware. Use them only for authorized testing in an isolated environment. This portal does not host exploit code — it only points to the sources.
EPSS over time FIRST
Oct 13, 2026 → Oct 16, 2026 · 4 reading(s) · max 97.03%
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
- Monitor file creation in web directories and paths with traversal sequences (../).
- Hunt retroactively in logs from before Nov 3, 2021 (KEV listing): exploitation may have started earlier.
Timeline
What happened to this CVE, newest first.
- 2026
- Affected products added · atlassian/confluence
- SSVC assessment updated
- Record published
- Fix documented
- Affected products added · atlassian/confluence server
- CVSS changed · 8.8
- Source status changed · → Analyzed
- Added to CISA KEV (detected)
- Record created in this database
- 2021
- Added to CISA KEV catalog
- 2019
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 2× References added · Oct 13, 2026 – Oct 13, 2026
- 1× Official description updated · Oct 13, 2026 – Oct 13, 2026
References
9 on the record
- jira.atlassian.com/browse/CONFSERVER-58102
- www.cisa.gov/known-exploited-vulnerabilities-catalog
- packetstormsecurity.com/files/152616/Confluence-Server-Data-Center-Path-Traversal.html
- packetstormsecurity.com/files/155245/Atlassian-Confluence-6.15.1-Directory-Traversal.html
- nvd.nist.gov/vuln/detail/CVE-2019-3398
- seclists.org/bugtraq/2019/Apr/33
- packetstormsecurity.com/files/155235/Atlassian-Confluence-6.15.1-Directory-Traversal.html
- github.com/advisories/GHSA-qv34-rfhx-fg2q
- www.securityfocus.com/bid/108067
Elsewhere on this site
Related CVEs (same products)
- Critical CVE-2026-21580 Cross-site Scripting (XSS) in Atlassian Confluence Data Center Aug 18, 2026
- High CVE-2025-22166 This High severity DoS (Denial of Service) vulnerability was introduced in version 2.0… Oct 21, 2025
- Critical CVE-2023-22527 Atlassian Confluence Data Center and Server Template Injection Vulnerability KEV Jan 16, 2024
- Critical CVE-2023-22518 Atlassian Confluence Data Center and Server Improper Authorization Vulnerability KEV Oct 31, 2023
- Critical CVE-2023-22515 Atlassian Confluence Data Center and Server Broken Access Control Vulnerability KEV Oct 4, 2023
- Critical CVE-2022-26134 Atlassian Confluence Server and Data Center Remote Code Execution Vulnerability KEV Jun 3, 2022
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2019-3398 is "Atlassian Confluence Server and Data Center Path Traversal Vulnerability", rated High. It affects Confluence (Atlassian); versions are in the scope table. It is in CISA KEV: there is evidence of real-world exploitation. CVSS 8.8 describes technical severity. EPSS 97.03% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.