CVE-2026-54459: CWE-352: Cross-Site Request Forgery (CSRF) in error311 FileRise
Description
FileRise versions prior to 3.14.0 have a Cross-Site Request Forgery (CSRF) vulnerability affecting the file creation and share-link creation endpoints. These endpoints do not enforce server-side CSRF token validation, allowing an attacker to perform unauthorized state-changing actions using a logged-in user's session. The vulnerability is mitigated somewhat by the default SameSite=Lax cookie setting. The issue is fixed in version 3.14.0.
CVSS v3.1
Score 4.3medium
Affected software
error311
FileRise
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
FileRise, a self-hosted web-based file manager, prior to version 3.14.0, fails to enforce server-side CSRF token checks on the POST endpoints /api/file/createFile.php and /api/file/createShareLink.php. These endpoints invoke FileController::createFile and FileController::createShareLink without rejecting requests missing a valid X-CSRF-Token header. As a result, an attacker can leverage a logged-in user's session to create empty files or share links without proper authorization. The default SameSite=Lax session cookie setting reduces the risk of cross-site POST requests but does not eliminate it. This vulnerability is addressed in FileRise version 3.14.0.
Potential Impact
An attacker can exploit this vulnerability to perform unauthorized file creation or share link creation actions on behalf of an authenticated user. This could lead to unauthorized sharing or creation of files, potentially impacting the integrity of the user's data or sharing settings. There is no impact on confidentiality or availability reported. The risk is reduced by the SameSite=Lax cookie attribute, which limits cross-site POST request reachability.
Mitigation Recommendations
Upgrade FileRise to version 3.14.0 or later, where this CSRF vulnerability has been fixed by enforcing server-side CSRF token validation on the affected endpoints. Until the upgrade, users should be aware of the risk and consider additional protective measures such as restricting access to trusted networks or using web application firewalls to detect and block CSRF attempts.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-06-15T15:30:40.318Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 6acd5cd82cdf04f656dece6e
Added to database: 10/12/2026, 22:19:04 UTC
Last enriched: 10/12/2026, 22:33:15 UTC
Last updated: 10/12/2026, 22:33:15 UTC
Views: 4
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.