# CVE-2025-14432: Poly Video - Sensitive Data Might Be Written to Log File

> Admins using Microsoft Teams Admin Center may inadvertently expose sensitive data in log files accessible only to other administrators.

- **Severity:** High 8.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:A/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 16 Dec 2025
- **Updated:** 17 Dec 2025
- **Also known as:** GHSA-jr38-4278-53pj

## What is CVE-2025-14432?

CVE-2025-14432 is a high-severity vulnerability in HP Inc Poly EagleEye Cube, published on 16 Dec 2025. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

In limited scenarios, sensitive data might be written to the log file if an admin uses Microsoft Teams Admin Center (TAC) to make device configuration changes. The affected log file is visible only to users with admin credentials. This is limited to Microsoft TAC and does not affect configuration changes made using the provisioning server or the device WebUI.

Weakness: CWE-532 (Insertion of Sensitive Information into Log File)

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

It affects 2 products.


Products: Hp Poly Tcos, Hp Poly Videoos.

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

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

## Is CVE-2025-14432 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-14432 is a high-severity vulnerability in HP Inc Poly EagleEye Cube, published on 16 Dec 2025. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2025-14432 in the wild and no public exploit code.

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

## Sources

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

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