CVE-2024-38909: Studio 42 elFinder 2.1.64 is vulnerable to Incorrect Access Control

This month

CRITICAL 9.8REMOTEDOWNGRADE

CVE-2024-38909 is a critical-severity flaw (CVSS 9.8) affecting elfinder. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

Studio 42 elFinder 2.1.64 is vulnerable to Incorrect Access Control. Copying files with an unauthorized extension between server directories allows an arbitrary attacker to expose secrets, perform RCE, etc.

Why this priority

Critical severity
Remotely exploitable, no login, no user action

No fix is published yet: follow the downgrade or mitigation steps.

Risk facts

CVSS score	9.8 (Critical)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	0.5% (top 59%)
CISA exploited list	No
Weakness	CWE-284
Published	2024-07-30
Last modified	2026-07-09

Publisher (CNA): MITRE · Vendor: std42

Last updated 2026-07-09 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2024-07-30 14:15 UTCPublished CVE record published
2026-07-09 01:19 UTCUpdated Record last modified

std42 elfinder DOWNGRADE

Affected: 2.1.64

Fixed in: no fixed release known

Safe to downgrade to: a release before 2.1.64

1. Check installed version

apt-cache policy elfinder || rpm -q elfinder || elfinder --version

2. No fixed release: DOWNGRADE to a release before 2.1.64 (Debian / Ubuntu)

apt-cache madison elfinder sudo apt install elfinder=<VERSION_BEFORE_2.1.64> sudo apt-mark hold elfinder

2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list elfinder sudo dnf downgrade elfinder-<VERSION_BEFORE_2.1.64> sudo dnf versionlock add elfinder

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2024-38909?

elfinder: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2024-38909 being exploited?

CVE-2024-38909 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2024-38909 affect?

CVE-2024-38909 affects elfinder. Severity is critical (CVSS 9.8). Studio 42 elFinder 2.1.64 is vulnerable to Incorrect Access Control. Copying files with an unauthorized extension between server directories allows an arbitrary attacker to expose secrets, perform RCE, etc.

How urgent is CVE-2024-38909?

Priority 50/100. Critical severity; Remotely exploitable, no login, no user action

Related CVEs

CVE-2026-41247 CRITICAL 9.8 UPGRADE elFinder is an open-source file manager for web, written in JavaScript using jQuery UI
CVE-2023-52045 MEDIUM 6.1 DOWNGRADE Studio-42 eLfinder 2.1.62 contains a filename restriction bypass leading to a persistent Cross-site Scripting
CVE-2023-52044 CRITICAL 9.8 DOWNGRADE Studio-42 eLfinder 2.1.62 is vulnerable to Remote Code Execution (RCE) as there is no restriction for uploadin
CVE-2023-35840 MEDIUM 6.5 UPGRADE _joinPath in elFinderVolumeLocalFileSystem.class.php in elFinder before 2.1.62 allows path traversal in the PH
CVE-2022-27115 CRITICAL 9.8 DOWNGRADE In Studio-42 elFinder 2.1.60, there is a vulnerability that causes remote code execution through file name byp

References

← Back to latest CVEs