How severe is GHSA-mvvp-gwgc-5hrp?

GHSA-mvvp-gwgc-5hrp has a CVSS score of 7.5/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-mvvp-gwgc-5hrp?

GHSA-mvvp-gwgc-5hrp affects the following packages: elFinder.Net.Core (NuGet). Ecosystems affected: NuGet.

How do I fix GHSA-mvvp-gwgc-5hrp?

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.

How do I detect GHSA-mvvp-gwgc-5hrp in my NuGet dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for elFinder.Net.Core. 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.

How do I mitigate GHSA-mvvp-gwgc-5hrp if there is no patch (or I can't update yet)?

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 does O3 Security protect against GHSA-mvvp-gwgc-5hrp?

O3 pinpoints whether GHSA-mvvp-gwgc-5hrp is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-mvvp-gwgc-5hrp actively exploited in the wild?

Yes. There are 1 known exploit references for GHSA-mvvp-gwgc-5hrp, including 1 in-the-wild exploitation observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

When was GHSA-mvvp-gwgc-5hrp published, and has it been updated?

GHSA-mvvp-gwgc-5hrp was published on August 2, 2021 and was last updated on July 8, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

.NET

.NET NuGet

Not in CISA KEV

HIGH severity

GHSA-mvvp-gwgc-5hrp

HIGHFix: trannamtrung1st/elFinder.Net.Core@5498c8a

GHSA-mvvp-gwgc-5hrp is a high-severity (CVSS 7.5) vulnerability in elFinder.Net.Core. 1 public exploit reference exists, so weaponization risk is real. O3 Security confirms whether GHSA-mvvp-gwgc-5hrp is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Path Traversal in elFinder.Net.Core

Also known asCVE-2021-23407SNYK-DOTNET-ELFINDERNETCORE-1315152

Published

Aug 2, 2021

Updated

Jul 8, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

1 known

Exploitation data as of Jul 8, 2026 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

.NETelFinder.Net.Core

Real-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

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
.NETNuGet	`elFinder.Net.Core`	all versions	1.2.4

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

This affects the package elFinder.Net.Core from 0 and before 1.2.4. The …

snyk.ioNVDAug 2021

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for elFinder.Net.Core. 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 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
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-mvvp-gwgc-5hrp 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-mvvp-gwgc-5hrp. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

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.

O3 Security · Impact-Aware SCA

Is GHSA-mvvp-gwgc-5hrp in your dependencies?

O3 detects GHSA-mvvp-gwgc-5hrp across NuGet dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works