Error311 FileRise
FileRise: Folder Metadata Filename Collisions Bypass "read_own" Isolation
FileRise is a self-hosted web-based file manager with multi-file upload, editing, and batch operations. Prior to 3.18.0, FileRise flattens logical folder paths into metadata filenames by replacing separators and spaces with hyphens, so distinct folders such as team/docs and team-docs can share one metadata file. Because uploader metadata is used to authorize read_own and ownership-restricted edits, a low-privileged user who controls one colliding folder, knows the target basename, and already has read_own access to the target folder can alter the metadata used by that folder, make the victim file appear attacker-owned, read it, and modify it when edit-own permission is also available. This issue is fixed in version 3.18.0.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- < 3.18.0
Fixed in 3.18.0
Mitigation
Upgrade FileRise to 3.18.0 or later.
References
- Vendor advisory github.com/error311/FileRise/security/advisori…
- Patch github.com/error311/FileRise/commit/9ed1a38f00…
- Release notes github.com/error311/FileRise/releases/tag/v3.1…
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.