# CVE-2025-54789: Files is Vulnerable to Reflected Self-XSS through its File Move Functionality

> Attackers can execute arbitrary JavaScript in user sessions via the File Move functionality in the HumHub Files module.

- **Severity:** Medium 5.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N`)
- **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:** 1 Aug 2025
- **Updated:** 4 Aug 2025
- **Also known as:** GHSA-cw2v-c62w-5r43

## What is CVE-2025-54789?

CVE-2025-54789 is a medium-severity cross-site scripting vulnerability in humhub cfiles, published on 1 Aug 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

Files is a module for managing files inside spaces and user profiles. In versions 0.16.9 and below, the File Move functionality does not contain logic that prevents injection of arbitrary JavaScript, which can lead to Browser JS code execution in the context of the user’s session. This is fixed in version 0.16.10.

Weakness: CWE-80 (Improper Neutralization of Script-Related HTML Tags in a Web Page)

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

It affects 1 product.


Products: Humhub Files.

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

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

## Is CVE-2025-54789 being exploited?

There is no known exploitation of CVE-2025-54789 in the wild and no public exploit code.

## Other vulnerabilities in humhub cfiles

- [CVE-2025-54790](https://insights.sbomify.com/CVE-2025-54790/): Files: Potential for SQL Injection through File Browse and List Operations (critical 9.2)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-54789 is a medium-severity cross-site scripting vulnerability in humhub cfiles, published on 1 Aug 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2025-54789 in the wild and no public exploit code.

Affected product: humhub cfiles. 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-54789/ (Markdown: https://insights.sbomify.com/CVE-2025-54789/index.md)
```

## Sources

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

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