dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2026-44521

HIGH · 8.8 CVSS v3.1 Published 2026-05-27
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
elFinder is an open-source file manager for web, written in JavaScript using jQuery UI. Prior to 2.1.68, 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. This vulnerability is fixed in 2.1.68.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

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

MitigationUpgrade elFinder to version 2.1.68 or later; if MySQL volume driver is not required, consider disabling it to reduce attack surface.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify elFinder version
    Locate the elFinder version file (commonly version.php, composer.json, or the main elfinder.js file) and read the declared version number
    Affected if Version is below 2.1.68
  2. Confirm MySQL volume driver is in use
    Check elFinder configuration files for instances of 'MySQL' or 'elFinderVolumeMySQL' in volume driver definitions
    Affected if MySQL driver is configured as a volume backend
  3. Verify driver is enabled
    Inspect the connector configuration to confirm the MySQL volume driver class is loaded and accessible
    Affected if The MySQL volume driver class is loaded and accessible to the connector
  4. Confirm user authentication is active
    Check if elFinder authentication is enabled and users can log in
    Affected if User authentication is enabled and users have access to the connector
  5. Check for external network exposure
    Review web server access controls to determine if the elFinder connector endpoint is exposed to untrusted networks
    Affected if The connector is reachable from untrusted networks without additional access controls

The environment is affected if elFinder version is below 2.1.68 AND the MySQL volume driver is configured and enabled in the connector configuration.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade elFinder to version 2.1.68 or later; if MySQL volume driver is not required, consider disabling it to reduce attack surface.

Recommended fix High confidence

elFinder 2.1.68

  1. 1. Identify if your elFinder installation uses the MySQL volume driver (elFinderVolumeMySQL). Check your volume configuration in the connector settings for 'driver' set to 'MySQL'.
  2. 2. If using the MySQL volume driver, upgrade elFinder to version 2.1.68 or later. Download from the official repository or package manager.
  3. 3. After upgrading, verify the elFinder version by checking the loaded JavaScript files or the connector response to confirm version 2.1.68 is in use.
  4. 4. Test that the file manager functionality works correctly with the MySQL volume after the upgrade.
  5. 5. If not using the MySQL volume driver, this vulnerability does not affect your installation, but consider upgrading to the latest version for other security fixes.

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-44521 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-44521 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data