Read the docs
TI-2026-71341 Aliases CVE-2026-54459

Missing CSRF checks in FileRise file and share-link creation

Priority MEDIUM 53CWE-352Published · Updated

Key facts

Attack vector
Network
Privileges required
None
User interaction
Required
Attack complexity
Low
Impact type
Tampering
Confidentiality · integrity · availability
None · Low · None
Fix status
Fixed

Attack profile from CVSS 3.1 · CNA. Fix status from CNA. Impact type from CWE-352.

Summary

FileRise from error311 before 3.14.0 does not enforce its server-side CSRF token check on file creation and share-link creation. The POST endpoints accept requests without a valid X-CSRF-Token header (CWE-352). A remote attacker needs a logged-in user to trigger a request from their browser, which can create an empty file or a share link with that user's permissions, although the default SameSite=Lax session cookie limits cross-site POST requests.

Written with Claude Haiku 5.5 from the sources below · 2026-10-29

Description from the CNA

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.

Why it matters now

Exploitation Proof of concept CISA SSVC · not in CISA KEV
EPSS 0.00118 1st percentileScored 2026-11-07
Fix Fixed FileRise (error311): 3.14.0

SSVC decision points

CISA ADP · SSVC 2.0.3

Exploitation
Poc
Automatable
No
Technical impact
Partial

The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.

Affected products

VendorProductAffected versionsFixed inStatusSource
error311FileRisebefore 3.14.03.14.0Patch availableCNA
  • FileRise Vendorerror311 Affected before 3.14.0 Fixed in 3.14.0 Patch available CNA

CPE names Threatist (inferred) · 1

Inferred from how NVD named this product before; not given by a source.

CPEVersionsRoleVendor
cpe:2.3:a:filerise:filerise:*:*:*:*:*:*:*:*——error311
  • cpe:2.3:a:filerise:filerise:*:*:*:*:*:*:*:* Versions — — ·error311

Remediation

Upgrade FileRise to version 3.14.0, which fixes this issue.

Written with Claude Haiku 5.5 from the sources below · 2026-10-29

  • Fix · CNA FileRise (error311) Fixed in 3.14.0

Timeline

  1. 2026-10-12 Threatist record created from CVE-2026-54459
  2. 2026-10-13 CISA SSVC decision points changed
  3. 2026-10-13 Priority changed: LOW → MEDIUM

References

Other 2

  • TI-2026-74499 Unauthenticated file overwrite in FileRise via upload-enabled shares CVSS 3.1HIGH 8.2
  • TI-2026-25514 FileRise: Default Encryption Key Enables Token Forgery and Config Decryption CVSS 3.1HIGH 8.2
  • TI-2025-41705 FileRise vulnerable to Cross-Site Scripting (XSS) in SVG File Handling CVSS 3.1HIGH 8.9
  • TI-2026-25513 FileRise: WebDAV upload path bypasses filename validation enforced by regular uploads CVSS 3.1HIGH 8.8
  • TI-2026-74495 WebDAV authentication in FileRise skips TOTP two-factor check CVSS 3.1HIGH 8.1
  • TI-2026-74494 Authentication bypass in FileRise via spoofed reverse-proxy headers CVSS 3.1HIGH 8.1
See all 37 →

Sources

This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences