# CVE-2025-2819: Unrestricted Fileupload

> An authenticated privileged user can upload arbitrary files due to insufficient validation, leading to data integrity issues and unauthorized access.

- **Severity:** Medium 6.6 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 Mar 2025
- **Updated:** 26 Mar 2025
- **Also known as:** GHSA-j6w5-x2v9-vjvh

## What is CVE-2025-2819?

CVE-2025-2819 is a medium-severity vulnerability in Bizerba SE & Co. KG GT-SoftControl, published on 26 Mar 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

There is a risk of unauthorized file uploads in GT-SoftControl and potential file overwrites due to insufficient validation in the file selection process. This could lead to data integrity issues and unauthorized access by an authenticated privileged user.

Weakness: CWE-434 (Unrestricted Upload of File with Dangerous Type)

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


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

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

## Is CVE-2025-2819 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-2819 is a medium-severity vulnerability in Bizerba SE & Co. KG GT-SoftControl, published on 26 Mar 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-2819 in the wild and no public exploit code.

Affected product: Bizerba SE & Co. KG GT-SoftControl. 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-2819/ (Markdown: https://insights.sbomify.com/CVE-2025-2819/index.md)
```

## Sources

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

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