Skip to main content
VulnerabilityPublished

CVE-2025-68116: error311 FileRise · Cross-site Scripting

Affects error311 FileRiseSource CVE Database V5

0

Not known to be exploited · CVSS 8.9 High : upgrade to 2.7.1 soon.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score
8.9High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 18% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2.7.1
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:L

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 16 Dec 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade error311/FileRise to 2.7.1.

Affected software

ProductAffectedFixed in
GitHuberror311/FileRisepkg:github/error311/FileRiseOther threatsAffected
  • <2.7.1
Fixed in
  • 2.7.1

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

  1. Upgrade FileRise to version 2.7.1 or later immediately to apply the official patch that fixes the XSS vulnerability.
  2. Implement strict file upload controls to restrict allowed file types, especially blocking SVG and HTML files unless absolutely necessary.
  3. Employ Content Security Policy (CSP) headers to restrict the execution of inline scripts and reduce the impact of potential XSS attacks.
  4. Monitor and audit file uploads and share link usage to detect suspicious activity or uploads of potentially malicious files.
  5. Educate users about the risks of opening untrusted shared links or files, emphasizing caution with files received from unknown or untrusted sources.
  6. If upgrading is not immediately possible, consider disabling or restricting access to the vulnerable share and download endpoints to limit exposure.
  7. Use web application firewalls (WAFs) with rules designed to detect and block XSS payloads targeting these endpoints.
  8. Regularly review and update security policies around file sharing and user privileges to minimize the risk of malicious uploads.

Description

FileRise is a self-hosted web file manager / WebDAV server. Versions prior to 2.7.1 are vulnerable to Stored Cross-Site Scripting (XSS) due to unsafe handling of browser-renderable user uploads when served through the sharing and download endpoints. An attacker who can get a crafted SVG (primary) or HTML (secondary) file stored in a FileRise instance can cause JavaScript execution when a victim opens a generated share link (and in some cases via the direct download endpoint). This impacts share links (`/api/file/share.php`) and direct file access / download path (`/api/file/download.php`), depending on browser/content-type behavior. Version 2.7.1 fixes the issue.

References

Community reviews

Loading reviews…