An issue was discovered in OpenEMR before 5.0.1 Patch 7.

published 2019-05-17 7y ago modified 2026-06-17 4mo ago also EUVD-2018-8954

cvss: 5.3; version 3.0, NVD
cisa kev: Not listed; not in CISA's catalog
epss: 1.9%; EPSS 1.9% chance of exploitation in 30 days, percentile 79%
public exploits: 0; none known

An issue was discovered in OpenEMR before 5.0.1 Patch 7. Directory Traversal exists via docid=../ to /portal/lib/download_template.php.

Patch / fix

fixed in 1 links 2

open-emr openemr 5.0.1.7

Is CVE-2018-17180 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

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

CVSS scores

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

Classification

Weakness

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

References

github.com /openemr/openemr/commit/4963fe4932a0a4e1e982642226174e9931d09541
patch, third-party-advisory
open-emr.org /wiki/index.php/OpenEMR_Patches#5.0.1_Patch_.289.2F9.2F18.29
patch, vendor-advisory

Sources

CVE List CVE-2018-17180
NVD CVE-2018-17180

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.