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

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

8.8 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

EPSS

• CVE-2026-44521: 0.24% estimated exploitation activity in the next 30 days; percentile 15.59 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

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…

Published by the source

11 May 2026, 16:11 UTC

Last modified by the source

8 Jun 2026, 23:49 UTC

Source last checked

26 Oct 2026, 14:48 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-c3gj-q88f-7hqj

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-44521

Advisory: elFinder MySQL has a SQL Injection in its Volume Driver (elFinderVolumeMySQL)
IDs: CVE-2026-44521, GHSA-c3gj-q88f-7hqj
Record: https://patchnext.com/advisories/cve-2026-44521 (revision 1, source checked 26 Oct 2026, 14:48 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.8)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: studio-42/elfinder 2.1.68. A vendor fix does not mean a deployment is fixed.

## Affected components
- Packagist studio-42/elfinder: affected <= 2.1.67; fixed in 2.1.68

## Suggested inspection (read-only)
- Packagist studio-42/elfinder: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on studio-42/elfinder.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-c3gj-q88f-7hqj (GitHub-reviewed advisory GHSA-c3gj-q88f-7hqj lists affected ranges: Packagist studio-42/elfinder >=0 <=2.1.67)

Commands are suggestions: review each one before running it.