CVE-2025-62509: FileRise is a self-hosted web-based file manager with multi-file upload, editing, and batch operations. Prior to…
CVE-2025-62509 · Severity: high · CVSS 8.1 · Published 2025-10-20
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.
No. Junglewise Threat Intelligence has no report of CVE-2025-62509 being exploited in the wild.
How severe is CVE-2025-62509?
High severity, with a CVSS score of 8.1, published 20 October 2025.
Which products and versions are affected?
Filerise. The advisory does not name versions.
Is there a fix for CVE-2025-62509?
No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
Am I affected by CVE-2025-62509?
Check whether you run Filerise. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.