# CVE-2025-50184: DbGate allows for File Traversal via file parameter

> Attackers can read arbitrary system files by manipulating the file parameter in DbGate, potentially exposing sensitive data.

- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:L/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 Jul 2025
- **Updated:** 28 Jul 2025
- **Also known as:** GHSA-2fp9-29gv-p5gm

## What is CVE-2025-50184?

CVE-2025-50184 is a high-severity path traversal vulnerability in dbgate, published on 26 Jul 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

DbGate is cross-platform database manager. In versions 6.4.3-premium-beta.5 and below, DbGate is vulnerable to a directory traversal flaw. The file parameter is not properly restricted to the intended uploads directory. As a result, the endpoint that lists files within the upload directory can be manipulated to access arbitrary files on the system. By supplying a crafted path to the file parameter, an attacker can read files outside the upload directory, potentially exposing sensitive system-level data. This is fixed in version 6.4.3-beta.8.

Weakness: CWE-29 (Path Traversal: '\..\filename')

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


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

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

## Is CVE-2025-50184 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-50184 is a high-severity path traversal vulnerability in dbgate, published on 26 Jul 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-50184 in the wild and no public exploit code.

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

## Sources

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

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