Authenticated cross-user file takeover via inherited root scope
Published Aug 14, 2026 · Updated Aug 14, 2026
Improper access control in File Browser before 2.63.20 allows remote authenticated users to access other users' files via proxy or hook auth. Proxy and hook auto-provisioning pass the default scope of "." into MakeUserDir, which normalizes it to the server root instead of deriving a per-user directory. The flaw requires createUserDir with the default scope and a valid upstream identity, granting read, write, delete, rename, and share access across the root.
Summary
What happened
Improper access control in File Browser before 2.63.20 allows remote authenticated users to access other users' files via proxy or hook auth. Proxy and hook auto-provisioning pass the default scope of "." into MakeUserDir, which normalizes it to the server root instead of deriving a per-user directory. The flaw requires createUserDir with the default scope and a valid upstream identity, granting read, write, delete, rename, and share access across the root.
The record
- CVE
- CVE-2026-72837
- Published
- Aug 14, 2026
- Updated
- Aug 14, 2026
- Vendor
- File Browser
- Product
- File Browser
- Classifications
- CWE-284, CWE-863, T1078
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 14, 2026CVE publishedPublication date reported by the CVE source.
- Aug 14, 2026Record 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=0 <2.63.20
What conditions does exploitation require?
What is affected?
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
- Vendor proxy and hook authentication proof of conceptproof of concept · demonstrated
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