# CVE-2025-6076: CVE-2025-6076

> An authenticated attacker can upload malicious files to compromise the device, potentially gaining SYSTEM privileges due to default configuration.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **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:** 2 Aug 2025
- **Updated:** 3 Nov 2025
- **Also known as:** GHSA-v5qq-h69f-g539

## What is CVE-2025-6076?

CVE-2025-6076 is a high-severity vulnerability in Partner Web, published on 2 Aug 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Partner Software's Partner Software application and Partner Web application do not sanitize files uploaded on the "reports" tab, allowing an authenticated attacker to upload a malicious file and compromise the device. By default, the software runs as SYSTEM, heightening the severity of the vulnerability.

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


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

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

## Is CVE-2025-6076 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-6076 is a high-severity vulnerability in Partner Web, published on 2 Aug 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-6076 in the wild and no public exploit code.

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

## Sources

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

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