ElfinderApplication · Std42

CVE-2026-41247

CRITICAL · 9.8 CVSS v3.1 Published 2026-04-23
Fix available
A fix is available. Upgrade to 2.1.67 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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.67, elFinder contains a command injection vulnerability in the resize command. The bg (background color) parameter is accepted from user input and passed through image resize/rotate processing. In configurations that use the ImageMagick CLI backend, this value is incorporated into shell command strings without sufficient escaping. An attacker able to invoke the resize command with a crafted bg value may achieve arbitrary command execution as the web server process user. This vulnerability is fixed in 2.1.67.

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

elFinder before 2.1.67 contains a command injection vulnerability in the resize command where the bg (background color) parameter is passed to ImageMagick CLI commands without proper escaping. An attacker able to supply a crafted bg value can achieve arbitrary command execution as the web server user.

MitigationUpgrade elFinder to version 2.1.67 or later. Additionally, verify if the ImageMagick CLI backend is in use and consider using the GD library backend as an alternative if feasible.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
ElfinderApplication
Affected:< 2.1.67

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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/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
    Check the version.php or changelog file in the elFinder installation directory, or inspect the elFinder JavaScript/connector file for a version string
    Affected if The installed version is before 2.1.67
  2. Confirm ImageMagick CLI backend is in use
    Inspect elFinder configuration (usually connector.php or a config JSON file) for the 'imagemagick' or 'imagick' backend setting in the driver or volume configuration
    Affected if ImageMagick is configured as the image processing backend (not GD library)
  3. Verify resize command is available
    Check elFinder configuration for the 'resize' command in the commands array or disabledCommands setting
    Affected if The resize command is enabled and accessible to users
  4. Check for exposed connector endpoint
    Identify if the elFinder connector (typically php/connector.php or similar) is accessible without authentication or from untrusted sources
    Affected if The connector is reachable without proper access controls, allowing external bg parameter injection

You are affected if elFinder version is below 2.1.67 AND the ImageMagick CLI backend is configured AND the resize command is enabled AND the connector is accessible to untrusted users.

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
Upgrade available Upgrade to 2.1.67 or later
Fixed in 2.1.67
Interim mitigation

Upgrade elFinder to version 2.1.67 or later. Additionally, verify if the ImageMagick CLI backend is in use and consider using the GD library backend as an alternative if feasible.

Recommended fix High confidence

elFinder 2.1.67

  1. Upgrade elFinder to version 2.1.67 or later to resolve the command injection vulnerability in the resize command.

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

Fix this in Elfinder Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

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-41247 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