Read the docs
TI-2026-74483 Aliases CVE-2026-103988

Authorization bypass in FileRise renameFolder endpoint

Priority MEDIUM 58CWE-284Published · Updated

Key facts

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

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

Summary

FileRise, a self-hosted web file manager, is affected in versions before 3.23.0. The renameFolder endpoint checks access to the source folder but does not independently check the destination parent folder. An authenticated, non-administrator user who owns a source folder can move it beneath another user's folder or into the root namespace, and the moved ownership and ACL records are rekeyed to the new path. Existing victim files cannot be overwritten, and the flaw is classified as CWE-639.

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

Description from the CNA

FileRise is a self-hosted web-based file manager with multi-file upload, editing, and batch operations. Prior to 3.23.0, FileRise /api/folder/renameFolder.php authorizes an authenticated, non-folder-scoped, non-administrator with a valid CSRF token against the source folder but does not independently authorize a changed destination parent. A qualifying user who owns a source folder can move that tree beneath another user's existing folder or into the root namespace, and the operation rekeys the moved ownership and ACL records to the new path. The destination must be unused and existing victim files cannot be overwritten. Distinct pre-fix errors reveal whether a specifically guessed destination path exists, but disclose no directory listing or file contents. This issue is fixed in version 3.23.0.

Why it matters now

Exploitation Proof of concept CISA SSVC · not in CISA KEV
EPSS 0.00229 13th percentileScored 2026-11-07
Fix Fixed FileRise (error311): 3.23.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.23.03.23.0Patch availableCNA
  • FileRise Vendorerror311 Affected before 3.23.0 Fixed in 3.23.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.23.0, which fixes this issue.

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

  • Fix · CNA FileRise (error311) Fixed in 3.23.0

Timeline

  1. 2026-10-15 Threatist record created from CVE-2026-103988
  2. 2026-10-15 CISA SSVC decision points changed

References

  • 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