CVE-2025-62509: FileRise improper ownership/permission validation allowed cross-tenant file operations

Severity: high (CVSS 8.1 v3.1)
Exploited in the wild: not listed in CISA KEV
EPSS: 0.3% probability of exploitation in the next 30 days
Public exploit or detection template: none known
Published: 2025-10-20 · updated 2026-10-08
Weakness: CWE-280

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

error311 FileRise: before 1.4.0 — fixed in 1.4.0

How to fix

Upgrade to a fixed version: error311 FileRise 1.4.0. Check the vendor advisory for mitigations.

References

Get alerted when CVE-2025-62509 or the next vulnerability affects your stack