CVE-2026-44260
HighSummary
In versions prior to 4.08.010 of the efw4.X framework, the readonly flag set on the <efw:elFinder> JSP tag was intended to prevent file modifications. However, the lack of proper event handlers allows attackers to perform write operations by bypassing the user interface.
Risk Assessment
The organization is exposed to unauthorized file modifications, which could lead to data loss or the introduction of malicious software.
Recommendation
It is recommended to upgrade to version 4.08.010 or later to mitigate this vulnerability.
Other vulnerabilities in efw4.X
See all- CVE-2026-44258Critical
In versions prior to 4.08.010, the elfinder_checkRisk function in efw4.X does not validate the dst parameter used by elfinder_paste, allowing an attacker to copy or move files from the home directory to any arbitrary location by setting dst to a base64-encoded traversal path.
- CVE-2026-44257Critical
In efw4.X prior to version 4.08.010, the efw.file.FileManager.unZip method did not check the canonical path when writing zip entries to disk, allowing for directory traversal. An attacker could exploit this vulnerability to drop a malicious JSP file and execute arbitrary commands as the Tomcat user.
Original NVD description (English source)
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.