vulntracker.iovulntracker.io
© 2026 vulntracker.io

CVE-2025-14432

Poly Video - Sensitive Data Might Be Written to Log File

MEDIUM
4.9
CVSS Score
Published: December 16, 2025 at 03:15 PM UTC
Updated: October 7, 2026 at 11:10 AM UTC
19 products affected across 1 vendorPoly TcosPoly VideoosPoly Studio G7500

Using Poly G7500 by HP Inc?

Get instant alerts when new vulnerabilities affect Poly G7500 - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Start FreeSign In
Severity
MEDIUM4.9
Exploit prediction
EPSS 0.4%
SSVC
No known exploit

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

Poly Tcos· HP
95%
v < 6.6.1-7001859
Affected range stops below 6.6.1-7001859, so it looks safe — our inference, not a vendor statement
hp-poly-tc10 (same device) · hp-poly-tc8 (same device)
Poly Videoos· HP
95%
v < 4.6.1-444242
Affected range stops below 4.6.1-444242, so it looks safe — our inference, not a vendor statement
hp-poly-eagleeye-cube (environment) · hp-poly-eagleeye-iv (environment) · hp-poly-studio-a2 (environment) · hp-poly-studio-e60 (environment) · hp-poly-studio-e70 (environment) · hp-poly-studio-g62 (environment) · hp-poly-studio-g7500 (environment) · hp-poly-studio-usb (environment) · hp-poly-studio-x30 (environment) · hp-poly-studio-x32 (environment) · hp-poly-studio-x50 (environment) · hp-poly-studio-x52 (environment) · hp-poly-studio-x70 (environment) · hp-poly-studio-x72 (environment)
Poly EagleEye Cube· HP
60%
v < <PolyOS 4.6.1-444242
Affected range stops below <PolyOS 4.6.1-444242, so it looks safe — our inference, not a vendor statement
Poly EagleEye IV· HP
60%
v < <PolyOS 4.6.1-444242
Affected range stops below <PolyOS 4.6.1-444242, so it looks safe — our inference, not a vendor statement
Poly G7500· HP
60%
v < <PolyOS 4.6.1-444242
Affected range stops below <PolyOS 4.6.1-444242, so it looks safe — our inference, not a vendor statement
Poly Studio A2· HP
60%
v < <PolyOS 4.6.1-444242
Affected range stops below <PolyOS 4.6.1-444242, so it looks safe — our inference, not a vendor statement
Poly Studio E60· HP
60%
v < <PolyOS 4.6.1-444242
Affected range stops below <PolyOS 4.6.1-444242, so it looks safe — our inference, not a vendor statement
Poly Studio E70· HP
60%
v < <PolyOS 4.6.1-444242
Affected range stops below <PolyOS 4.6.1-444242, so it looks safe — our inference, not a vendor statement
Poly Studio G62· HP
60%
v < <PolyOS 4.6.1-444242
Affected range stops below <PolyOS 4.6.1-444242, so it looks safe — our inference, not a vendor statement
Poly Studio USB· HP
60%
v < <PolyOS 4.6.1-444242
Affected range stops below <PolyOS 4.6.1-444242, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

Patch and advisory references

References (1)

Vendor Advisory
Source: cverecord
https://support.hp.com/us-en/document/ish_13612310-13612332-16/hpsbpy04080

SSVC — Action Prioritization

SSVCNo known exploitNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

4.9MEDIUM[email protected]
Attack Vector
NETWORK
Complexity
LOW
Privileges
HIGH
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
HIGH
Integrity
NONE
Availability
NONE
Vector?

Quick Info

StatusANALYZED
CWE
CWE-532

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Create accountSign in
Free plan, no card