Skip to main content
CVE-2025-14432VulnerabilityPublished Updated

CVE-2025-14432: HP Poly G7500 · Sensitive Data in Logs

Affects HP Poly G7500Source CVE Database V5

0

Not known to be exploited · CVSS 8.1 High.

Data as of 26 Oct 2026, 07:57 UTC

CVSS 4.0 base score
8.1High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 33% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 16 Dec 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

What to do

Affected software

ProductAffectedFixed in
HP Inc Poly G7500Affected
  • =0
Fixed in–

AI-suggested

1. Restrict access to Microsoft Teams Admin Center (TAC) strictly to trusted administrators and enforce strong multi-factor authentication to reduce the risk of credential compromise. 2. Limit access to log files on Poly G7500 devices to only essential personnel and implement strict file permissions and audit logging to detect unauthorized access. 3. Regularly review and sanitize logs to remove sensitive information where feasible, or implement log management solutions that redact sensitive data. 4. Monitor administrative activities and log access patterns for anomalies that could indicate exploitation attempts or insider threats. 5. Coordinate with HP Inc and Microsoft for any available patches or updates addressing this vulnerability and apply them promptly once released. 6. Consider using alternative configuration methods (provisioning server or device WebUI) that are not affected by this vulnerability until a fix is available. 7. Educate administrators about the risks of sensitive data exposure in logs and best practices for secure device management. 8. Employ network segmentation to isolate management interfaces and reduce exposure to potential attackers.

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.

References

Community reviews

Loading reviews…