Skip to content

Product

std42 elfinder vulnerabilities

16 published CVES affecting std42 elfinder, from public sources (CVE.org, NVD, CISA KEV, FIRST EPSS, OSV).

Total
16
Critical
10
High
2
Medium
4
Low
0
Unscored
0
CISA KEV
0

Latest std42 elfinder CVEs

Newest publication first

  1. CriticalCVSS 9.1 EPSS 51.0%

    connector.minimal.php in std42 elFinder through 2.1.60 is affected by path traversal. This allows unauthenticated remote attackers to read, write, and browse files outside the configured document root. This is due to improper handling of absolute file paths.

  2. CriticalCVSS 9.8 EPSS 68.5% Framework module Public exploit

    elFinder is an open-source file manager for web, written in JavaScript using jQuery UI. 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 m...

  3. CriticalCVSS 9.8 EPSS 18.9%

    The package studio-42/elfinder before 2.1.58 are vulnerable to Remote Code Execution (RCE) via execution of PHP code in a .phar file. NOTE: This only applies if the server parses .phar files as PHP.

  4. HighCVSS 7.7 EPSS 1.1% PoC

    A Server Side Request Forgery (SSRF) vulnerability in elFinder before 2.1.46 could allow a malicious user to access the content of internal network resources. This occurs in get_remote_contents() in php/elFinder.class.php.

  5. CriticalCVSS 9.1 EPSS 2.9% PoC

    Studio 42 elFinder before 2.1.37 has a directory traversal vulnerability in elFinder.class.php with the zipdl() function that can allow a remote attacker to download files accessible by the web server process and delete files owned by the account running the web server process. N...

  6. CriticalCVSS 9.1 EPSS 2.9% PoC

    Studio 42 elFinder before 2.1.36 has a directory traversal vulnerability in elFinder.class.php with the zipdl() function that can allow a remote attacker to download files accessible by the web server process and delete files owned by the account running the web server process.

Sources: CVE.org, NVD, CISA KEV, FIRST EPSS, OSV and public exploit-reference metadata. Product matching comes from the published CVE records. A proof-of-concept means public code exists; it is not evidence of exploitation.