# CVE-2025-54790: Files: Potential for SQL Injection through File Browse and List Operations

> An attacker can exploit SQL injection in file browse and list operations to access unauthorized data in the HumHub Files plugin.

- **Severity:** Critical 9.2 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 Aug 2025
- **Updated:** 4 Aug 2025
- **Also known as:** GHSA-rfvq-g9rm-pgqj

## What is CVE-2025-54790?

CVE-2025-54790 is a critical SQL injection vulnerability in humhub cfiles, published on 1 Aug 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Files is a module for managing files inside spaces and user profiles. In versions 0.16.9 and below, Files does not have logic to prevent the exploitation of backend SQL queries without direct output, potentially allowing unauthorized data access. This is fixed in version 0.16.10.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

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

It affects 1 product.


Products: Humhub Files.

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

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

## Is CVE-2025-54790 being exploited?

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

## Other vulnerabilities in humhub cfiles

- [CVE-2025-54789](https://insights.sbomify.com/CVE-2025-54789/): Files is Vulnerable to Reflected Self-XSS through its File Move Functionality (medium 5.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-54790 is a critical SQL injection vulnerability in humhub cfiles, published on 1 Aug 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-54790 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-54790/ (Markdown: https://insights.sbomify.com/CVE-2025-54790/index.md)
```

## Sources

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

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