# CVE-2025-68116: FileRise vulnerable to Cross-Site Scripting (XSS) in SVG File Handling

> Attackers can execute arbitrary JavaScript in victims' browsers by uploading malicious SVG or HTML files to FileRise, leading to potential session hijacking or data theft.

- **Severity:** High 8.9 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 16 Dec 2025
- **Updated:** 16 Dec 2025
- **Also known as:** GHSA-35pp-ggh6-c59c

## What is CVE-2025-68116?

CVE-2025-68116 is a high-severity cross-site scripting vulnerability in error311 FileRise, published on 16 Dec 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official 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.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

## Which versions are affected by CVE-2025-68116?

It affects 1 product.


Products: Filerise Filerise.

## How do I fix CVE-2025-68116?

No fix has been published for CVE-2025-68116 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-68116 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-68116 exists.

Public exploit code:

- A Documentation of CVE-2025-68116 (github_poc): https://github.com/x0root/CVE-2025-68116

## Other vulnerabilities in error311 FileRise

- [CVE-2026-33072](https://insights.sbomify.com/CVE-2026-33072/): FileRise: Default Encryption Key Enables Token Forgery and Config Decryption (high 8.2)
- [CVE-2026-33329](https://insights.sbomify.com/CVE-2026-33329/): Path traversal in FileRise (high 8.1)
- [CVE-2025-62509](https://insights.sbomify.com/CVE-2025-62509/): FileRise improper ownership/permission validation allowed cross-tenant file operations (high 8.1)
- [CVE-2025-62510](https://insights.sbomify.com/CVE-2025-62510/): FileRise insecure folder visibility via name-based mapping and incomplete ACL checks (high 8.1)
- [CVE-2026-25231](https://insights.sbomify.com/CVE-2026-25231/): FileRise affected by an Unauthenticated File Read Due to Insufficient Access Control (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-68116 and fix it if it is affected.

What it is: CVE-2025-68116 is a high-severity cross-site scripting vulnerability in error311 FileRise, published on 16 Dec 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-68116 exists.

Affected product: error311 FileRise. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-68116/ (Markdown: https://insights.sbomify.com/CVE-2025-68116/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-68116
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-68116
- OSV: https://osv.dev/vulnerability/CVE-2025-68116

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-68116/
Summaries are generated and may contain mistakes; the official description above is the record.