How severe is CVE-2019-18393?

CVE-2019-18393 has a CVSS score of 5.3/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2019-18393?

CVE-2019-18393 affects the following packages: org.igniterealtime.openfire:parent (Maven). Ecosystems affected: Maven.

How do I fix CVE-2019-18393?

Update org.igniterealtime.openfire:parent to 4.5.0-beta or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2019-18393 is resolved across your whole dependency graph.

How do I detect CVE-2019-18393 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.igniterealtime.openfire:parent, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2019-18393 if there is no patch (or I can't update yet)?

Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.

Is CVE-2019-18393 actively exploited in the wild?

No public exploit code has been indexed for CVE-2019-18393 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2019-18393?

CVE-2019-18393 has an EPSS (Exploit Prediction Scoring System) score of 13.9%, placing it in the 97th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score warrants monitoring and prompt remediation.

What type of vulnerability is CVE-2019-18393?

CVE-2019-18393 is classified as Path Traversal (CWE-22). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

Is there exploit tooling available for CVE-2019-18393?

A Nuclei detection template exists for CVE-2019-18393, meaning automated scanners can fingerprint it. Public exploit tooling significantly increases real-world risk — prioritize patching and ensure detection coverage. Exploit tooling should only ever be used in isolated, authorized testing environments.

When was CVE-2019-18393 published, and has it been updated?

CVE-2019-18393 was published on October 24, 2019 and was last updated on October 20, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕

☕ Maven

Not in CISA KEV

MEDIUM severity

CVE-2019-18393 — parent

MEDIUMFix: igniterealtime/Openfire#1498

CVE-2019-18393 is a medium-severity (CVSS 5.3) Path Traversal vulnerability in org.igniterealtime.openfire:parent. EPSS puts its 30-day exploitation probability at 13.9% (97th percentile). A fix is available for org.igniterealtime.openfire:parent — see the affected versions and patch details below.

Ignite Realtime Openfire directory traversal vulnerability

Also known asGHSA-59h8-h34r-q9cv

Published

Oct 24, 2019

Updated

Oct 20, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 5, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

13.9%probability of exploitation in next 30 days

Moderate Risk0.00%

Lower risk than most CVEs97th percentile — riskier than 97% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected

☕org.igniterealtime.openfire:parent

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

PluginServlet.java in Ignite Realtime Openfire through 4.4.2 does not ensure that retrieved files are located under the Openfire home directory, aka a directory traversal vulnerability. Version 4.5.0-beta contains a fix for the issue.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.igniterealtime.openfire:parent`	all versions	4.5.0-beta`org.igniterealtime.openfire:parent:4.5.0-beta`

Affected Products

1 product · 1 configurations

Application

openfireigniterealtime

≤ 4.4.2

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.igniterealtime.openfire:parent, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.igniterealtime.openfire:parent to 4.5.0-beta or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2019-18393 is resolved across your whole dependency graph.
Workarounds
Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.

How to detect CVE-2019-18393

A community-maintained Nuclei template exists for this CVE. You can scan for it directly:

nuclei -id cve-2019-18393 -u https://target

Template: Ignite Realtime Openfire <4.42 - Local File Inclusion
Severity: medium
Impact: Successful exploitation of this vulnerability can lead to unauthorized access to sensitive information, remote code execution, and potential compromise of the affected system.
Remediation: Upgrade Ignite Realtime Openfire to version 4.42 or later to mitigate this vulnerability.

Template by ProjectDiscovery nuclei-templates (pikpikcu), MIT licensed. View the full template. Scan only systems you are authorised to test.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2019-18393 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

5.3/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

Low

Integrity

None

Availability

None

Raw vector

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

CWE Classification

Weaponization

OpenSSF Scorecard

Package health score

Openfire

3.6/10

Code-Review9/10

Maintained10/10

Branch-Protection0/10

Assessed Oct 19, 2026

Timeline

Disclosed

Oct 24, 2019

Last updated

Oct 20, 2026

Identifiers

CVE-2019-18393

GHSA-59h8-h34r-q9cv

References

Advisorynvd.nist.gov · CVE 2019 18393 Fixgithub.com Webswarm.ptsecurity.com · openfire admin console Webgithub.com · cb900749d4e836b32cc6e2cc41cda17f252b977d Webswarm.ptsecurity.com · openfire admin console

Related vulnerabilities

This CVE is medium severity; 8 of 8 other CVEs affecting parent are rated as high or higher (top: critical).

CVE-2019-20527CVE-2019-20526CVE-2019-20525CVE-2019-20366CVE-2019-18394CVE-2014-2741CVE-2017-15911CVE-2018-11688

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedOct 20, 2026

CVE-2019-18393 — parent

EPSS Exploitation Probability

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

Description

Affected Packages

Affected Products

Detection & mitigation playbook

Detect

Fix

Workarounds

How to detect CVE-2019-18393

Frequently Asked Questions

Is CVE-2019-18393 in your dependencies?