🛡️ CVE-2026-44521 — elfinder

🟠 CVSS 8.8 — High ✅ No Known Exploit CWE-89 NVD
8.8
CVSS Score
0 Low4 Medium7 High9 Critical10

Description

elFinder MySQL has a SQL Injection in its Volume Driver (elFinderVolumeMySQL)

Summary

An authenticated SQL injection vulnerability in the elFinder MySQL volume driver (elFinderVolumeMySQL) allows any logged-in user, including users with read-only access to the affected volume, to inject SQL through a crafted target file hash. Successful exploitation can lead to unauthorized data disclosure and denial of service.

This vulnerability only affects installations configured to use the MySQL volume driver. Installations using the default LocalFileSystem driver are not affected.

Description

A vulnerability in elFinder's MySQL volume driver (elFinderVolumeMySQL) allows authenticated SQL injection through a crafted file hash passed via the target parameter.

The issue is caused by two behaviors working together:

1. File hashes are decoded without validating that the decoded value is a valid MySQL object identifier.

2. The decoded value is then used in MySQL driver queries, including cacheDir(), _joinPath(), _stat(), and _fopen().

Because the MySQL storage schema uses numeric id and parent_id values, an authenticated user can supply a crafted hash that alters the intended SQL query logic. Successful exploitation can lead to unauthorized data disclosure and denial of service. The extent of impact depends on the privileges granted to the configured MySQL account.

This vulnerability only affects installations configured to use the MySQL volume driver. Installations using the default LocalFileSystem driver are not affected.

Impact

An authenticated user, including a user with read-only access to the affected volume, can exploit this issue to:

  • disclose data accessible to the configured MySQL account, including file contents stored by the driver and database metadata
  • trigger denial of service through expensive or unexpectedly broad query results that can lead to excessive memory consumption

The severity of data exposure depends on the privileges granted to the configured MySQL account.

How this vulnerability can be exploited

This issue can be reached over the network, attack complexity is low, an attacker needs low-level privileges on the target. No user interaction is required. The scope is unchanged, so the impact stays within the vulnerable component. Rated impact: confidentiality high, integrity high, availability high.

Weakness class

CVE-2026-44521 is classified as CWE-89: SQL Injection. Untrusted input is concatenated into an SQL statement, letting an attacker change the query and reach data the request should not return.

Affected software

CVE-2026-44521 is recorded against 2 packages.

  • studio-42/elfinder (fixed in 2.1.68)
  • unknown

Timeline and source

Published on 11 May 2026 and last revised on 9 June 2026. No public exploit is currently recorded for this entry. Record sourced from NVD.

References

github.com (Web)
nvd.nist.gov (Advisory)
github.com (Package)

Details

Severity HIGH
CVSS Score 8.8
CVSS Vector CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CWE CWE-89
Public Exploit ✅ No
Source NVD
Published 2026-05-11
Updated 2026-08-12
Modified 2026-06-09
Fix URL N/A

Affected Packages

Software From version Fixed in
studio-42/elfinder 2.1.68
unknown

Similar Threats

Site Security Check

Is elfinder part of your stack?

CVE-2026-44521 is rated CVSS 8.8 High. BotEraser scans your installation against known CVE records and tells you whether this vulnerability applies to the versions you actually run.

Scan My Site Free →

No credit card required  ·  Results in minutes

ⓘ Data Notice: The information presented above has been compiled from publicly available internet sources. Boteraser aggregates this data solely for informational purposes and does not independently classify, evaluate, or endorse any findings about the vulnerabilities listed. The accuracy and completeness of this information is the sole responsibility of the original publishers. Boteraser and its operators accept no liability for any decisions made based on this data.