All vulnerabilities
CVE-2026-104109GHSA-jp22-hh6w-mpwp

FileRise: Authenticated ZIP extraction follows a pre-existing symlink and deletes files outside the storage root

error311 FileRise
CVSS
6.8Medium
ExploitationNo known exploitationNot in CISA KEV, which does not prove it is unexploitedCISA KEV
Exploit odds (EPSS)0.32%Chance of exploitation activity in the next 30 days, higher than 24% of CVEs. Scored 23 Oct 2026FIRST EPSS
Fixed in3.23.0Fixed versionGitHub
Published14 Oct 2026Updated 14 Oct 2026CVE List

What fixes it

  • 3.23.0error311/FileRise, otherGitHub

A fixed version on one release line is not the upgrade target for every line. Check your exact version and any vendor backports.

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.

Text from CVE List

Affected versions 2

  • FileRiseaffected: < 3.23.0CVE List
  • error311/FileRise, other<= 3.22.0GitHub

References 3