CVE-2018-15535 in the critical feed json
/filemanager/ajax_calls.php in tecrail Responsive FileManager before 9.13.4 uses external input to construct a pathname that should be with…
published 8y ago modified 4mo ago also EUVD-2018-7411
- cvss
- 7.5
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 44.8%
- EPSS 44.8% chance of exploitation in 30 days, percentile 98%
- public exploits
- 1
- Exploit-DB, plus a Nuclei check
Summary
/filemanager/ajax_calls.php in tecrail Responsive FileManager before 9.13.4 uses external input to construct a pathname that should be within a restricted directory, but it does not properly neutralize get_file sequences such as ".." that can resolve to a location that is outside of that directory, aka Directory Traversal.
Patch / fix
- tecrail responsive_filemanager 9.13.4
Is CVE-2018-15535 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 FencerTimeline
- Published
- First public exploit (EDB-45271)
Exploit prediction
44.81% chance of exploitation in the next 30 days, higher than 98% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- EDB-45271 Responsive FileManager < 9.13.4 - Directory Traversal webapps, 2018-08-27
- Nuclei template Responsive FileManager <9.13.4 - Local File Inclusion nuclei detection template
- seclists.org http://seclists.org/fulldisclosure/2018/Aug/34 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 7.5 | CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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
-
exploit-db.com
/exploits/45271/
exploit, third-party-advisory, vdb-entry
-
seclists.org
/fulldisclosure/2018/Aug/34
mailing-list, exploit, third-party-advisory
Sources
- CVE List CVE-2018-15535
- NVD CVE-2018-15535
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.