Vulnerability · Published Oct 20, 2025 · Assigned by GitHub_M
CVE-2025-62509FileRise improper ownership/permission validation allowed cross-tenant file operations
High 8.1
In plain English
A high-severity improper access control in FileRise from error311. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.3% (higher than 23% of all known vulnerabilities).
Official description
FileRise is a self-hosted web-based file manager with multi-file upload, editing, and batch operations. Prior to version 1.4.0, a business logic flaw in FileRise’s file/folder handling allows low-privilege users to perform unauthorized operations (view/delete/modify) on files created by other users. The root cause was inferring ownership/visibility from folder names (e.g., a folder named after a username) and missing server-side authorization/ownership checks across file operation endpoints. This amounted to an IDOR pattern: an attacker could operate on resources identified only by predictable names. This issue has been patched in version 1.4.0 and further hardened in version 1.5.0. A workaround for this issue involves restricting non-admin users to read-only or disable delete/rename APIs server-side, avoid creating top-level folders named after other usernames, and adding server-side checks that verify ownership before delete/rename/move.
Affected products (as reported)
Weakness: CWE-280, CWE-284 · Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
References
- https://github.com/error311/FileRise/security/advisories/GHSA-6p87-q9rh-95wh x_refsource_CONFIRM
- https://github.com/error311/FileRise/issues/53 x_refsource_MISC
- https://github.com/error311/FileRise/commit/25ce6a76beb60950359c0304765ad91a8aff8ad8 x_refsource_MISC