CVE-2018-9110 json
Directory Traversal in Studio 42 elFinder
published 2018-03-28 8 y ago modified 2026-06-17 4 mo ago also GHSA-44p8-c3wv-f28r , EUVD-2022-2296
- cvss
- 9.1
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.9%
- EPSS 2.9% chance of exploitation in 30 days, percentile 86%
- public exploits
- 0
- none known
Summary
Studio 42 elFinder before 2.1.37 has a directory traversal vulnerability in elFinder.class.php with the zipdl() function that can allow a remote attacker to download files accessible by the web server process and delete files owned by the account running the web server process. NOTE: this issue exists because of an incomplete fix for CVE-2018-9109.
Patch / fix
- packagist studio-42/elfinder 2.1.37
- std42 elfinder 2.1.37
Exploit prediction
2.88% chance of exploitation in the next 30 days, higher than 86% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 9.1 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N |
| NVD | 2.0 | 7.5 | AV:N/AC:L/Au:N/C:P/I:P/A:P |
| GitHub | 3.1 | 9.1 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| packagist | studio-42/elfinder | >=2.1.12, <2.1.37 |
2.1.37 |
Classification
- Weakness
-
- CWE-22 Improper Limitation of a Pathname to a Restricted Directory
References
-
github.com
/Studio-42/elFinder/commit/e6351557b86cc10a7651253d2d2aff7f6b918f8e
web, patch, third-party-advisory
-
github.com
/Studio-42/elFinder/releases/tag/2.1.37
web, release-notes, third-party-advisory
-
github.com
/Studio-42/elFinder/wiki/Advisory-about-vulnerability-of-CVE-2018-9109-and-CVE-2018-9110
web, mitigation, third-party-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2018-9110
advisory
Sources
- CVE List CVE-2018-9110
- GitHub Advisory GHSA-44p8-c3wv-f28r
- NVD CVE-2018-9110
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.