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

Published Oct 20, 2025
·
Updated

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 Software

2 affected components
FileRise FileRise<1.4.0
FileRise FileRise<1.4.0

Event History

Oct 20, 2025
CVE Published
via MITRE·05:38 PM
Data Sourced
via MITRE·05:38 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·06:15 PM
RemedyDescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2025-62509?

CVE-2025-62509 is classified as a high severity vulnerability due to its potential for unauthorized file operations by low-privilege users.

2

How do I fix CVE-2025-62509?

To fix CVE-2025-62509, upgrade FileRise to version 1.4.0 or later, which addresses the business logic flaw.

3

Who is affected by CVE-2025-62509?

CVE-2025-62509 affects all users of FileRise versions prior to 1.4.0.

4

What types of operations can be exploited in CVE-2025-62509?

CVE-2025-62509 allows low-privilege users to perform unauthorized operations such as viewing, deleting, or modifying files.

5

Is there a workaround for CVE-2025-62509 if I cannot upgrade immediately?

Currently, there are no known workarounds for CVE-2025-62509, and it is strongly recommended to upgrade to the latest version.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203