{"id":"CVE-2026-57491","title":"FileRise is a self-hosted web-based file manager with multi-file upload, editing, and batch operations","summary":"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() writ…","severity":"medium","cvss":6.5,"cvssVector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N","cwe":["CWE-434"],"vendor":"error311","product":"FileRise","affected":["FileRise < 3.16.0"],"published":"2026-10-14","updated":"2026-10-15","sourceUpdated":"2026-10-15T19:17:41.620","source":"NVD","sourceUrl":"https://nvd.nist.gov/vuln/detail/CVE-2026-57491","references":[{"url":"https://github.com/error311/FileRise/commit/f7114ca2a4e624238dda0d097a07ad6b05c11bb6","label":"security-advisories@github.com"},{"url":"https://github.com/error311/FileRise/releases/tag/v3.16.0","label":"security-advisories@github.com"},{"url":"https://github.com/error311/FileRise/security/advisories/GHSA-c4g2-8fg6-5xrr","label":"security-advisories@github.com"},{"url":"https://github.com/error311/FileRise/security/advisories/GHSA-c4g2-8fg6-5xrr","label":"134c704f-9b21-4f2e-91b3-4a467353bcc0"}],"tags":["nvd","cve.org","exploit-available"],"exploitAvailable":true,"ssvc":{"exploitation":"poc","automatable":"no","technicalImpact":"partial","timestamp":"2026-10-15T18:51:39.878344Z"},"ingestedAt":"2026-10-14T21:57:04.824Z","epss":0.00349,"epssPercentile":0.28341,"slug":"CVE-2026-57491","body":"## Overview\n\nFileRise 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.\n\n## Remediation\n\nRefer to the linked advisories for vendor-supplied fixes and affected version ranges.","depth":"twilight","depthScore":48,"depthScoreParts":{"impact":35.8,"likelihood":0.1,"exploitation":12,"ransomware":0},"changes":[{"seq":222669,"id":"CVE-2026-57491","ts":1792092498989,"field":"exploit_available","old":"false","new":"true"}]}