CVE-2026-54459 FileRise: Missing CSRF enforcement for file creation and share-link creation
Attackers can trick logged-in users into creating files or share links via CSRF, allowing unauthorized data modification in FileRise.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- A user has to click or open something
- Fix
- None listed
What is CVE-2026-54459?
CVE-2026-54459 is a medium-severity vulnerability in error311 FileRise, published on 12 Oct 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Official description
FileRise is a self-hosted web-based file manager with multi-file upload, editing, and batch operations. Prior to 3.14.0, FileRise authenticates requests to the file creation and share-link creation handlers but does not enforce the server-side CSRF token check used by adjacent state-changing operations. The POST endpoints /api/file/createFile.php and /api/file/createShareLink.php invoke FileController::createFile and FileController::createShareLink without rejecting a missing or invalid X-CSRF-Token header. A request issued with a logged-in user's session can create an empty file or create a share link with that user's permissions, although the default SameSite=Lax session cookie reduces ordinary cross-site POST reachability. This issue is fixed in version 3.14.0.
Weakness: CWE-352
Which versions are affected by CVE-2026-54459?
How do I fix CVE-2026-54459?
No fix has been published for CVE-2026-54459 yet. Limit exposure of the affected software until one is available.
Is CVE-2026-54459 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-54459 exists.
Sources
Also known as GHSA-jp5j-9px9-g47g.