CVE-2022-40734 json
UniSharp Laravel Filemanager directory traversal vulnerability
published 2022-09-14 4 y ago modified 2026-06-17 4 mo ago also GHSA-5m2h-7rf2-rpx6 , EUVD-2022-6710
- cvss
- 6.5
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 5.5%
- EPSS 5.5% chance of exploitation in 30 days, percentile 92%
- public exploits
- 0
- none known, plus a Nuclei check
Summary
UniSharp laravel-filemanager (aka Laravel Filemanager) before 2.6.4 allows download?working_dir=%2F.. directory traversal to read arbitrary files, as exploited in the wild in June 2022. This is related to league/flysystem before 2.0.0.
Patch / fix
Exploit prediction
5.53% chance of exploitation in the next 30 days, higher than 92% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- Nuclei template Laravel Filemanager v2.5.1 - Local File Inclusion nuclei detection template
- github.com https://github.com/UniSharp/laravel-filemanager/issues/1150 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N |
| GitHub | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| packagist | unisharp/laravel-filemanager | <2.6.4 |
2.6.4 |
Classification
- Weakness
-
- CWE-22 Improper Limitation of a Pathname to a Restricted Directory
References
-
github.com
/UniSharp/laravel-filemanager/commit/8a357d02e8f54ddf130961c64ff2cfc1882bbfcf
web
-
github.com
/UniSharp/laravel-filemanager/issues/1150
web, exploit, issue-tracking, third-party-advisory
-
github.com
/UniSharp/laravel-filemanager/issues/1150#issuecomment-1320186966
web
-
github.com
/UniSharp/laravel-filemanager/issues/1150#issuecomment-1825310417
web
-
nvd.nist.gov
/vuln/detail/CVE-2022-40734
advisory
-
github.com
/UniSharp/laravel-filemanager
package
Sources
- CVE List CVE-2022-40734
- GitHub Advisory GHSA-5m2h-7rf2-rpx6
- NVD CVE-2022-40734
Fencer Vulns 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.