CVE-2018-9109: elFinder Path Traversal vulnerability in studio-42/elfinder

studio-42/elfinder Updated 02 Oct 2025

Summary

13/05/2022
Yes i
Critical
9.1

CVE-2018-9109: elFinder Path Traversal vulnerability. Affects studio-42/elfinder versions < 2.1.36. Fixed in 2.1.36. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

studio-42/elfinder is a package available on Packagist that provides a file manager for web applications. It allows users to browse, upload, and manage files and folders on a server. The package is widely used and integrated into various web applications. However, a vulnerability has been discovered in versions prior to 2.1.36 that allows for path traversal attacks.

Vulnerability Detail

The elFinder Path Traversal vulnerability in studio-42/elfinder allows a remote attacker to download files accessible by the web server process and delete files owned by the account running the web server process. This vulnerability exists in the elFinder.class.php file, specifically in the zipdl() function. By exploiting this vulnerability, an attacker can bypass file access restrictions and potentially gain unauthorized access to sensitive files or delete important data.

How To Fix

Minimum fixed version

2.1.36

This is the first release that contains the fix.

composer require studio-42/elfinder:2.1.36

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

If updating the package is not immediately feasible, a temporary workaround can be implemented by disabling the zipdl() function in the elFinder.class.php file. This can be achieved by commenting out or removing the relevant code block. However, it is important to note that this workaround only disables the vulnerable functionality and does not address the root cause of the vulnerability. Updating the package to the latest version is still the recommended long-term solution.

Conclusion

The elFinder Path Traversal vulnerability in studio-42/elfinder poses a significant risk to web applications utilizing this package. It allows for unauthorized file access and potential data loss. To mitigate this vulnerability, it is crucial to update the package to version 2.1.36 or later. If immediate updating is not feasible, a temporary workaround can be implemented by disabling the vulnerable zipdl() function. For further support and assistance in vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for studio-42/elfinder →

Share this vulnerability

FAQ

This vulnerability allows an attacker to download and potentially delete files accessible by the web server process. This can lead to unauthorized access to sensitive data or loss of important files.

You can use the Vulert Playground at Vulert Scanner to check if your application is affected by this vulnerability. Simply input your composer.lock file and the playground will analyze it for any open-source vulnerabilities, including this one.

While there are no known public exploits for this specific vulnerability at the time of writing, it is important to promptly update the package to mitigate the risk of potential exploitation.

While applying the workaround can temporarily disable the vulnerable functionality, it is still recommended to update the package to the latest version as soon as possible. Updating the package ensures a comprehensive fix for the vulnerability and provides long-term security.

In addition to updating the package, it is always recommended to follow secure coding practices and regularly review and update your application's dependencies. Keeping all software components up to date helps mitigate the risk of potential vulnerabilities.

Related vulnerabilities

Recent vulnerabilities recorded for studio-42/elfinder.

How To Fix

Minimum fixed version

2.1.36

This is the first release that contains the fix.

composer require studio-42/elfinder:2.1.36

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback