GHSA-wph3-44rj-92pr is a critical-severity (CVSS 9.8) Path Traversal vulnerability in studio-42/elfinder. 3 public exploit references exist, so weaponization risk is real. O3 Security confirms whether GHSA-wph3-44rj-92pr is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
elFinder before 2.1.59 contains multiple vulnerabilities leading to RCE
Real-World Exposure
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
We recently fixed several vulnerabilities affect elFinder 2.1.58. These vulnerabilities can allow an attacker to execute arbitrary code and commands on the server hosting the elFinder PHP connector, even with the minimal configuration.
Patches
The issues were addressed in our last release, 2.1.59.
Workarounds
If you can't update to 2.1.59, make sure your connector is not exposed without authentication.
Reference
Further technical details will be disclosed on https://blog.sonarsource.com/tag/security after some time.
For more information
If you have any questions or comments about this advisory, you can contact: - The original reporters, by sending an email to [email protected]; - The maintainers, by opening an issue on this repository.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | studio-42/elfinder | all versions | 2.1.59 |
Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
elFinder is an open-source file manager for web, written in JavaScript u…
elFinder is an open-source file manager for web, written in JavaScript u…
elFinder is an open-source file manager for web, written in JavaScript u…
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.59 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-wph3-44rj-92pr 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-wph3-44rj-92pr 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-wph3-44rj-92pr. 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-wph3-44rj-92pr in your dependencies?
O3 detects GHSA-wph3-44rj-92pr across Packagist dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.