Is CVE-2026-54459 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-54459 being exploited in the wild.

How severe is CVE-2026-54459?

Medium severity, with a CVSS score of 4.3, published 12 October 2026.

Which products and versions are affected?

Error311 FileRise prior to 3.14.0.

How is CVE-2026-54459 attacked?

It is attacked over the network or from the adjacent network, in a web application.

Am I affected by CVE-2026-54459?

Check whether you run Error311 FileRise at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-54459: FileRise missing CSRF enforcement for file creation

CVE-2026-54459 · Severity: medium · CVSS 4.3 · Published 2026-10-12

FileRise is a self-hosted web-based file manager that allows users to upload, edit, and manage files. Before version 3.14.0, the file creation and share-link creation endpoints did not properly validate CSRF tokens, allowing an attacker to create files or share links on behalf of a logged-in user without their knowledge. Although the default SameSite=Lax cookie setting limits practical cross-site exploitation, a malicious website could still trick a user's browser into performing these actions.

Technologies: Error311 FileRise. Vendors: Error311.

Quick answers

Is CVE-2026-54459 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-54459 being exploited in the wild.
How severe is CVE-2026-54459?: Medium severity, with a CVSS score of 4.3, published 12 October 2026.
Which products and versions are affected?: Error311 FileRise prior to 3.14.0.
Is there a fix for CVE-2026-54459?: Yes: fixed in 3.14.0. Until then: Ensure FileRise is upgraded to version 3.14.0 or later. If immediate patching is not possible, restrict network access to the FileRise application and monitor for suspicious file creation or share-link generation activity. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-54459 attacked?: It is attacked over the network or from the adjacent network, in a web application.
Am I affected by CVE-2026-54459?: Check whether you run Error311 FileRise at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

Fixed in: 3.14.0

Ensure FileRise is upgraded to version 3.14.0 or later. If immediate patching is not possible, restrict network access to the FileRise application and monitor for suspicious file creation or share-link generation activity.

Technical details

FileRise's POST endpoints /api/file/createFile.php and /api/file/createShareLink.php invoke FileController methods that call requireAuth() but fail to call checkCsrf() to validate the X-CSRF-Token header, unlike other state-changing file operations in the same controller. An authenticated attacker can send requests without a valid CSRF token to create empty files or generate share links with the victim's permissions. The vulnerability requires an authenticated session but bypasses the CSRF protection mechanism used elsewhere in the application.

Affected products

error311 FileRise prior to 3.14.0

Timeline

2026-06-15: disclosed
2026-06-15: patched: version 3.14.0 released
2026-10-12: advisory: CVE-2026-54459 published

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.