CVE-2022-40734 — unisharp/laravel-filemana…
MEDIUMCVE-2022-40734 is a medium-severity (CVSS 6.5) Path Traversal vulnerability in unisharp/laravel-filemanager. 2 public exploit references exist, so weaponization risk is real. A fix is available for unisharp/laravel-filemanager — see the affected versions and patch details below.
UniSharp Laravel Filemanager directory traversal vulnerability
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
How urgent is this, really
CVE-2022-40734 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 377,166 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
unisharp/laravel-filemanagerReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.
Description
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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | unisharp/laravel-filemanager | all versions | 2.6.4composer require unisharp/laravel-filemanager:^2.6.4 |
Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for unisharp/laravel-filemanager, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update unisharp/laravel-filemanager to 2.6.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-40734 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2022-40734 can be triaged on real exposure rather than presence alone.
Tailored to CVE-2022-40734. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
How to detect CVE-2022-40734
A community-maintained Nuclei template exists for this CVE. You can scan for it directly:
nuclei -id cve-2022-40734 -u https://target- Template
- Laravel Filemanager v2.5.1 - Local File Inclusion
- Severity
- medium
- Impact
- Successful exploitation of this vulnerability can lead to unauthorized access, sensitive data exposure, and remote code execution.
- Remediation
- Upgrade to a patched version of Laravel Filemanager v2.5.1 or apply the recommended security patches provided by the vendor.
Template by ProjectDiscovery nuclei-templates (arafatansari), MIT licensed. View the full template. Scan only systems you are authorised to test.
Frequently Asked Questions
Is CVE-2022-40734 in your dependencies?
O3 Security finds CVE-2022-40734 across Packagist dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.