Skip to main content
VulnerabilityPublished

CVE-2026-44260: efwGrp efw4.X · Incorrect Authorization

Affects efwGrp efw4.XSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 8.1 High : upgrade to 4.08.010 soon.

Data as of 29 Oct 2026, 19:04 UTC

CVSS 3.1 base score
8.1High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 28% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 4.08.010
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 12 May 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.

What to do

Upgrade efw4.X and efwgrp/efw4.X to 4.08.010.

Affected software

ProductAffectedFixed in
efwGrpefw4.XAffected
  • <4.08.010
Fixed in
  • 4.08.010
GitHubefwgrp/efw4.Xpkg:github/efwgrp/efw4.XOther threatsAffected
  • <4.08.010
Fixed in
  • 4.08.010

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A fix is available in efw4.X version 4.08.010. Users should upgrade to this version to remediate the vulnerability. Patch status is not explicitly confirmed beyond this version update, so verify with the vendor advisory for the latest remediation guidance.

Description

efw4.X is an Enterprise Framework for Web. Prior to 4.08.010, the readonly flag set on the <efw:elFinder> JSP tag is intended to prevent file modifications. When protected=true, elfinder_checkRisk enforces that the client sends readonly=true (matching the session value), but no event handler checks the readonly value before performing write operations. The flag only controls client-side UI elements (disabling buttons) and response metadata (write: 0, locked: 1). An attacker who sends requests directly (bypassing the UI) can perform all file operations despite readonly=true. This vulnerability is fixed in 4.08.010.

References

Community reviews

Loading reviews…