Is studio-42/elfinder vulnerable?

Composer studio-42/elfinder has 18 known advisories in the phpwarden feed. Feed 2026.10.29.1, updated 2026-10-28.

18advisories
9critical
0on CISA KEV
2no fix recorded
CVETitleSeverityCVSSAffectedFixed in
CVE-2019-9194elFinder command injection vulnerability in the PHP connectorcritical9.8<2.1.482.1.48
CVE-2021-32682elFinder before 2.1.59 contains multiple vulnerabilities leading to RCEcritical9.8<2.1.592.1.59
CVE-2022-26960Path Traversal in Studio-42 elFinder through 2.1.60critical9.1<2.1.612.1.61
CVE-2021-43421elFinder Unrestricted File Upload vulnerabilitycritical9.8>=2.0.4 and <2.1.602.1.60
CVE-2022-27115RCE in Studio-42 elFinder on Windows before 2.1.61critical9.8<2.1.612.1.61
CVE-2021-23394elFinder unsafe upload filtering leading to remote code executionhigh8.1<2.1.582.1.58
CVE-2018-9109elFinder Path Traversal vulnerabilitycritical9.1<2.1.362.1.36
CVE-2018-9110Directory Traversal in Studio 42 elFindercritical9.1>=2.1.12 and <2.1.372.1.37
CVE-2023-35840elFinder vulnerable to path traversal in LocalVolumeDriver connectorhigh7.5<2.1.622.1.62
CVE-2026-41247elFinder: Command injection in resize background color parameter when using ImageMagick CLIcritical9.8<2.1.672.1.67
CVE-2019-5884Sensitive Data Exposure in elFindermedium5.9<2.1.452.1.45
CVE-2019-6257elFinder Server Side Request Forgery (SSRF)high7.7<2.1.492.1.49
CVE-2026-81891elFinder: ZIP extraction bypasses uploadDeny MIME filter allowing PHP file upload (RCE)high8.1<2.1.702.1.70
CVE-2021-45919Studio 42 elFinder allows stored XSSmedium5.4<=2.1.31–
CVE-2026-81889elFinder: SSRF protection bypass via DNS rebinding in the `fsock_get_contents()` fallbackhigh8.6<2.1.702.1.70
CVE-2024-38909Studio 42 elFinder vulnerable to Incorrect Access Controlcritical9.8<=2.1.64–
CVE-2026-44521elFinder MySQL has a SQL Injection in its Volume Driver (elFinderVolumeMySQL)high8.8<2.1.682.1.68
CVE-2026-81890elFinder: CSRF in netmount allows forced FTP mounts and server-side FTP connectionsmedium5.4<2.1.702.1.70

Am I affected?

Find out in one command. phpwarden checks your composer.lock against this advisory and 20,000+ others, ranked by real-world exploitation (CISA KEV + EPSS). Free, offline, open data.

# one-time install
pip install phpwarden

# then
phpwarden deps composer.lock

Or keep it checked automatically: GitHub Action · pre-commit hook · GitLab CI · Laravel artisan command

Install docs   How findings are ranked
A version is vulnerable when it falls inside an affected range and below the fixed version. phpwarden applies these ranges to the exact versions in your lockfile or install, so you only see what applies to you.