FileRise: ZIP extraction writes blocked file extensions to disk, bypassing the upload blocklist
What fixes it
No source in this snapshot names a fixed version. The vendor advisories under References are the place to check.
Description
FileRise is a self-hosted web-based file manager with multi-file upload, editing, and batch operations. Prior to 3.16.0, FileRise archive extraction does not apply UploadNamePolicy::isAllowedForWrite() before ZipArchive::extractTo() writes entries into the destination directory. An authenticated user with upload and extract permissions can place a blocked extension such as a PHP-family file inside a ZIP and cause it to be written to disk even when normal uploads reject that filename. Post-extraction metadata pruning does not remove the blocked file, so deployments that execute uploaded content may permit code execution. This issue is fixed in version 3.16.0.
Text from CVE List
Affected versions 1
- FileRiseaffected: < 3.16.0CVE List