Path Traversal in elFinder.Net.CoreGHSA-mvvp-gwgc-5hrp
HIGHFix: trannamtrung1st/elFinder.Net.Core@5498c8aGHSA-mvvp-gwgc-5hrp is a high-severity (CVSS 7.5) Path Traversal vulnerability in elFinder.Net.Core. 1 public exploit reference exists, so weaponization risk is real. A fix is available for elFinder.Net.Core — see the affected versions and patch details below.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
GHSA-mvvp-gwgc-5hrp by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.
Where this sits among everything scored
Of 385,738 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.
Real-World Exposure
elFinder.Net.CoreReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects NuGet packages — download data is not available via public APIs for these ecosystems.
Description
This affects the package elFinder.Net.Core from 0 and before 1.2.4. The user-controlled file name is not properly sanitized before it is used to create a file system path.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| .NETNuGet | elFinder.Net.Core | all versions | 1.2.4dotnet add package elFinder.Net.Core --version 1.2.4 |
Affected Products
elfinder.net.coreelfinder.net.core_projectResearch 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 elFinder.Net.Core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update elFinder.Net.Core to 1.2.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-mvvp-gwgc-5hrp is resolved across your whole dependency graph.
Workarounds
Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.
Frequently Asked Questions
Is GHSA-mvvp-gwgc-5hrp in your dependencies?
Find it across NuGet, including transitive dependencies.