How severe is GHSA-6p96-vfrc-fv32?

GHSA-6p96-vfrc-fv32 has a CVSS score of 9.8/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by GHSA-6p96-vfrc-fv32?

GHSA-6p96-vfrc-fv32 affects the following packages: studio-42/elfinder (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-6p96-vfrc-fv32?

Update studio-42/elfinder to 2.1.61 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-6p96-vfrc-fv32 is resolved across your whole dependency graph.

How do I detect GHSA-6p96-vfrc-fv32 in my Packagist dependencies?

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.

How do I mitigate GHSA-6p96-vfrc-fv32 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-6p96-vfrc-fv32?

O3 pinpoints whether GHSA-6p96-vfrc-fv32 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-6p96-vfrc-fv32 actively exploited in the wild?

Yes. There are 1 known exploit references for GHSA-6p96-vfrc-fv32, 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.

What is the EPSS score for GHSA-6p96-vfrc-fv32?

GHSA-6p96-vfrc-fv32 has an EPSS (Exploit Prediction Scoring System) score of 28.9%, placing it in the 98th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score warrants monitoring and prompt remediation.

When was GHSA-6p96-vfrc-fv32 published, and has it been updated?

GHSA-6p96-vfrc-fv32 was published on April 12, 2022 and was last updated on February 16, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐘 Packagist

GHSA-6p96-vfrc-fv32

CRITICAL

RCE in Studio-42 elFinder on Windows before 2.1.61

Also known asCVE-2022-27115

Published

Apr 12, 2022

Updated

Feb 16, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

1 known

EPSS Exploitation Probability

via FIRST.org ↗

28.9%probability of exploitation in next 30 days

Moderate Risk98th percentile+14.13%

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.

Blast Radius

1 pkg affected

🐘studio-42/elfinder

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

In Studio-42 elFinder 2.1.60, there is a vulnerability that causes remote code execution through file name bypass for file upload.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`studio-42/elfinder`	all versions	2.1.61

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.

In Studio-42 elFinder 2.1.60, there is a vulnerability that causes remot…

github.comNVDApr 2022

Detection & mitigation playbook

Open-source dependency

Detect
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.61 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-6p96-vfrc-fv32 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-6p96-vfrc-fv32 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-6p96-vfrc-fv32. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

In Studio-42 elFinder 2.1.60, there is a vulnerability that causes remote code execution through file name bypass for file upload.

O3 Security · Impact-Aware SCA

Is GHSA-6p96-vfrc-fv32 in your dependencies?

O3 detects GHSA-6p96-vfrc-fv32 across Packagist 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