dbcve.org
OS Command InjectionWeakness · CWE-78

CVE-2026-44258

CRITICAL · 9.3 CVSS v4.0 Published 2026-05-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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
efw4.X is an Enterprise Framework for Web. Prior to 4.08.010, the elfinder_checkRisk function validates target and targets for path traversal and home containment, but does not validate the dst (destination) parameter used by elfinder_paste. An attacker can copy or move files from within the home directory to any arbitrary destination by setting dst to a base64-encoded traversal path. This bypasses the protected=true security control. This vulnerability is fixed in 4.08.010.

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

A path traversal vulnerability exists in efw4.X's elfinder component where the elfinder_checkRisk function validates the target and targets parameters but fails to validate the dst (destination) parameter used by elfinder_paste. An attacker can copy or move files from within the protected home directory to arbitrary locations by providing a base64-encoded traversal path in the dst parameter, bypassing the protected=true security control.

MitigationUpgrade to efw4.X version 4.08.010 or later which adds dst parameter validation to the elfinder_checkRisk function.

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
None
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

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 efw4.X installation version
    Locate the efw4.X version file or check the installed package version using the system package manager or web interface version display
    Affected if The installed version is before 4.08.010 (or the version cannot be determined but the product is efw4.X)
  2. Confirm elfinder component is present
    Search the efw4.X installation for elfinder-related files, typically in the web root or application modules directory
    Affected if The elfinder component directory or files exist on the system
  3. Verify elfinder_paste function is exposed
    Check the elfinder configuration and routing to determine if the paste command endpoint is accessible to users
    Affected if The elfinder_paste function is enabled and accessible via the web interface or API
  4. Inspect elfinder_checkRisk function for dst validation
    Locate and examine the elfinder_checkRisk function source code to determine if it validates the dst parameter
    Affected if The elfinder_checkRisk function exists but does NOT include validation logic for the dst parameter
  5. Check for base64 dst parameter handling in elfinder
    Search the elfinder code for dst parameter processing, specifically looking for base64 decoding without path traversal validation
    Affected if The code processes base64-encoded dst parameters without sanitizing for traversal sequences (..)

The environment is affected if running efw4.X versions before 4.08.010 with the elfinder component enabled and the elfinder_checkRisk function missing dst parameter validation.

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 to efw4.X version 4.08.010 or later which adds dst parameter validation to the elfinder_checkRisk function.

Recommended fix High confidence

efw4.X 4.08.010

  1. Identify the current installed version of efw4.X
  2. Download efw4.X version 4.08.010 from the official vendor source
  3. Backup the current efw4.X installation and configuration
  4. Stop the efw4.X service
  5. Install version 4.08.010
  6. Verify the elfinder_checkRisk function now validates the dst parameter
  7. Restart the efw4.X service
  8. Confirm the protected=true security control is enforced for copy/move operations via elfinder_paste

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
16.0 hours of engineering $2,760
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-44258 — 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-44258 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