GHSA-wm5g-p99q-66g4
HIGHGHSA-wm5g-p99q-66g4 is a high-severity (CVSS 7.5) Path Traversal vulnerability in studio-42/elfinder. 3 public exploit references exist, so weaponization risk is real. O3 Security confirms whether GHSA-wm5g-p99q-66g4 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
elFinder vulnerable to path traversal in LocalVolumeDriver connector
Blast Radius
studio-42/elfinderReal-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
Impact
Path Traversal vulnerability in PHP LocalVolumeDriver connector. This vulnerability can be exploited by allowing untrusted users to write to the local file system.
This issue was caused by incomplete validity checking of the supplied request parameters. That problem has been fixed in elFinder Version 2.1.62.
Patches
This vulnerability has been fixed in elFinder 2.1.62. Installation managers should update to the latest version as soon as possible.
Workarounds
If you cannot update for some reason, you must stop using it or prohibit writing to untrusted users.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | studio-42/elfinder | all versions | 2.1.62 |
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 studio-42/elfinder. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update studio-42/elfinder to 2.1.62 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-wm5g-p99q-66g4 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 pinpoints whether GHSA-wm5g-p99q-66g4 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to GHSA-wm5g-p99q-66g4. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-wm5g-p99q-66g4 in your dependencies?
O3 detects GHSA-wm5g-p99q-66g4 across Packagist dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.