# CVE-2025-0858: Certain Poly Devices – Path Traversal Vulnerability - Arbitrary File Access by Unauthorized User

> An unauthorized user can exploit a path traversal flaw in Poly device firmware to access arbitrary files and disclose sensitive information.

- **Severity:** Medium 5.8 (`CVSS:4.0/AV:A/AC:L/AT:P/PR:H/UI:N/VC:H/VI:L/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 Feb 2025
- **Updated:** 27 Mar 2025
- **Also known as:** GHSA-j3rg-cj85-6mq6

## What is CVE-2025-0858?

CVE-2025-0858 is a medium-severity path traversal vulnerability in HP, Inc. Certain Poly Devices, published on 5 Feb 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A vulnerability was discovered in the firmware builds up to 8.2.1.0820 in certain Poly devices. The firmware flaw does not properly prevent path traversal and could lead to information disclosure.

Weakness: CWE-35 (Path Traversal: '.../...//')

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


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

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

## Is CVE-2025-0858 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-0858 is a medium-severity path traversal vulnerability in HP, Inc. Certain Poly Devices, published on 5 Feb 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-0858 in the wild and no public exploit code.

Affected product: HP, Inc. Certain Poly Devices. 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-0858/ (Markdown: https://insights.sbomify.com/CVE-2025-0858/index.md)
```

## Sources

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

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