Cross-tenant file access via name-based authorization
Published Oct 20, 2025 · Updated Oct 20, 2025
Improper access control in error311 FileRise before 1.4.0 allows remote authenticated users to read, modify, or delete other users' files. File and folder operation endpoints infer ownership and visibility from predictable folder names instead of enforcing per-request read, write, and ownership checks. A non-admin account and a top-level folder whose name matches another user are sufficient to compromise file confidentiality and integrity without interrupting service.
Summary
What happened
Improper access control in error311 FileRise before 1.4.0 allows remote authenticated users to read, modify, or delete other users' files. File and folder operation endpoints infer ownership and visibility from predictable folder names instead of enforcing per-request read, write, and ownership checks. A non-admin account and a top-level folder whose name matches another user are sufficient to compromise file confidentiality and integrity without interrupting service.
The record
- CVE
- CVE-2025-62509
- Published
- Oct 20, 2025
- Updated
- Oct 20, 2025
- Vendor
- error311
- Product
- FileRise
- Classifications
- CWE-280, CWE-284, T1485, T1213
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Oct 20, 2025CVE publishedPublication date reported by the CVE source.
- Oct 20, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 1.4.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo