Skip to content
Fencer Intel
high 8.8

CVE-2019-3394 in the critical feed json

There was a local file disclosure vulnerability in Confluence Server and Confluence Data Center via page exporting.

published 7y ago modified 4mo ago also EUVD-2019-13033

cvss
8.8
version 3.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
11.0%
EPSS 11.0% chance of exploitation in 30 days, percentile 95%
public exploits
0
none known

Summary

There was a local file disclosure vulnerability in Confluence Server and Confluence Data Center via page exporting. An attacker with permission to editing a page is able to exploit this issue to read arbitrary file on the server under <install-directory>/confluence/WEB-INF directory, which may contain configuration files used for integrating with other services, which could potentially leak credentials or other sensitive information such as LDAP credentials. The LDAP credential will be potentially leaked only if the Confluence server is configured to use LDAP as user repository. All versions of Confluence Server from 6.1.0 before 6.6.16 (the fixed version for 6.6.x), from 6.7.0 before 6.13.7 (the fixed version for 6.13.x), and from 6.14.0 before 6.15.8 (the fixed version for 6.15.x) are affected by this vulnerability.

Patch / fix

  • Atlassian Confluence Server 6.6.16, 6.13.7, 6.15.8

Is CVE-2019-3394 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

11.02% chance of exploitation in the next 30 days, higher than 95% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 3.0 8.8 CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
NVD 2.0 4.0 AV:N/AC:L/Au:S/C:P/I:N/A:N

Affected products

  • Atlassian Confluence Server

Classification

Weakness
  • CWE-22 Improper Limitation of a Pathname to a Restricted Directory

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.