Impact
FileRise does not require a valid server‑side CSRF token for the POST endpoints that create files or share links. This flaw is a classic example of CWE‑352 (Cross‑Site Request Forgery), which allows an attacker who can force a victim to send a cookie‑authenticated request to create an empty file or an arbitrary share link with the victim’s permissions. The lack of CSRF enforcement means that authenticated users are able to perform these state‑changing operations without any additional verification, potentially leading to data modification or unintended data exposure.
Affected Systems
Self‑hosted instances of FileRise by error311, versions earlier than 3.14.0 are affected.
Risk and Exploitability
The CVSS score of 4.3 indicates a moderate impact. No EPSS score is available and the vulnerability is not listed in the CISA KEV catalog. The attack is likely to occur via a cross‑site POST that includes the victim’s session cookie; the default SameSite=Lax setting does not entirely prevent reachability but still allows the POST from an untrusted origin.
OpenCVE Enrichment