FileRise is a self-hosted web-based file manager with multi-file upload, editing, and batch…

Why it is Yellow

• CVSS 6.8 medium

References

• https://github.com/error311/FileRise/commit/cc1118923b522baff28dca05bdd79c27f984c68a
• https://github.com/error311/FileRise/releases/tag/v3.23.0
• https://github.com/error311/FileRise/security/advisories/GHSA-jp22-hh6w-mpwp

Original description

FileRise is a self-hosted web-based file manager with multi-file upload, editing, and batch operations. Prior to 3.23.0, FileRise validates archive entry names but extracts them directly into the authorized live destination before validating resolved paths. If that destination already contains a symlink to a directory outside the storage root, an authenticated non-administrator with extract permission who can upload or otherwise place an attacker-controlled ZIP in that folder can place an ordinary archive entry beneath the link. ZipArchive::extractTo() can then overwrite an external file, and post-extraction cleanup can delete that target through the same linked parent, only where the FileRise process has the required filesystem write or removal permission. The advisory does not establish that the attacker can create the prerequisite symlink through FileRise. This issue is fixed in version 3.23.0.