Description
FileRise is a self-hosted web-based file manager with multi-file upload, editing, and batch operations. Prior to 3.23.0, FileRise /api/folder/renameFolder.php authorizes an authenticated, non-folder-scoped, non-administrator with a valid CSRF token against the source folder but does not independently authorize a changed destination parent. A qualifying user who owns a source folder can move that tree beneath another user's existing folder or into the root namespace, and the operation rekeys the moved ownership and ACL records to the new path. The destination must be unused and existing victim files cannot be overwritten. Distinct pre-fix errors reveal whether a specifically guessed destination path exists, but disclose no directory listing or file contents. This issue is fixed in version 3.23.0.
Published: 2026-10-14
Score: 5.4 Medium
EPSS: < 1% Very Low
KEV: No
Impact: Privilege Escalation
Action: Apply Patch
AI Analysis

Impact

FileRise allows a non-administrator user who owns a folder to rename that folder to any parent folder that does not belong to the user or to the root namespace. The rename operation reassigns ownership and access control entries to the new location, effectively granting the user access to files that were originally protected. This does not overwrite existing files, but it does allow the attacker to move entire directory trees into another user’s space or into the top-level namespace, bypassing normal authorization checks that would normally prevent such cross-user moves. The vulnerability therefore enables unauthorized modification of file ownership and access rights, which can lead to confidential data exposure and unauthorized data manipulation.

Affected Systems

FileRise, a self-hosted web-based file manager, is affected in all releases prior to version 3.23.0. Any installation using these earlier versions can experience the described privilege escalation through the /api/folder/renameFolder.php endpoint.

Risk and Exploitability

The CVSS score of 5.4 indicates a medium severity vulnerability. The EPSS score is not available, and the issue is not currently listed in the CISA KEV catalog, suggesting that large-scale exploitation has not yet been observed. Attackers only need an authenticated account and a valid CSRF token; the operation can be performed through normal API traffic. Because the impact is limited to the application layer and does not involve arbitrary code execution or data loss outside the FileRise instance, the risk is moderate but still significant for organizations that rely on strict isolation of user data.

Generated by OpenCVE AI on October 15, 2026 at 12:42 UTC.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade FileRise to version 3.23.0 or later, which includes the access control fix for the renameFolder operation.
  • If an upgrade is not immediately possible, restrict renameFolder usage so that only the same user or an administrator can change the destination parent; apply a server-side rule blocking moves across user boundaries.
  • Implement logging of all renameFolder actions and routinely review logs for unauthorized move attempts to detect potential misuse early.

Generated by OpenCVE AI on October 15, 2026 at 12:42 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Thu, 15 Oct 2026 16:30:00 +0000

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'poc', 'Technical Impact': 'partial'}, 'version': '2.0.3'}


Wed, 14 Oct 2026 20:45:00 +0000

Type Values Removed Values Added
Description FileRise is a self-hosted web-based file manager with multi-file upload, editing, and batch operations. Prior to 3.23.0, FileRise /api/folder/renameFolder.php authorizes an authenticated, non-folder-scoped, non-administrator with a valid CSRF token against the source folder but does not independently authorize a changed destination parent. A qualifying user who owns a source folder can move that tree beneath another user's existing folder or into the root namespace, and the operation rekeys the moved ownership and ACL records to the new path. The destination must be unused and existing victim files cannot be overwritten. Distinct pre-fix errors reveal whether a specifically guessed destination path exists, but disclose no directory listing or file contents. This issue is fixed in version 3.23.0.
Title FileRise renameFolder omits destination-parent authorization
Weaknesses CWE-284
CWE-639
References
Metrics cvssV3_1

{'score': 5.4, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N'}


Subscriptions

No data.

cve-icon MITRE

Status: PUBLISHED

Assigner: GitHub_M

Published:

Updated: 2026-10-15T15:07:34.533Z

Reserved: 2026-10-01T16:09:08.456Z

Link: CVE-2026-103988

cve-icon Vulnrichment

Updated: 2026-10-15T15:07:01.811Z

cve-icon NVD

Status : Deferred

Published: 2026-10-14T21:17:34.000

Modified: 2026-10-15T16:17:33.020

Link: CVE-2026-103988

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-10-15T12:45:13Z

Weaknesses
  • CWE-284

    Improper Access Control

  • CWE-639

    Authorization Bypass Through User-Controlled Key