WebUI tampering via stored configuration XSS
Published Jul 8, 2026 · Updated Jul 8, 2026
Stored XSS in HP Poly CCX and Trio C60 before 9.5.0 and Edge E before 8.6.0 allows remote authenticated users to alter WebUI content. The phones store attacker-controlled input in configuration parameters and later render it as webpage content without neutralizing executable markup. Exploitation requires low-privileged configuration access and a user's passive visit to the affected WebUI, and the published impact is content modification rather than disclosure or service interruption.
Summary
What happened
Stored XSS in HP Poly CCX and Trio C60 before 9.5.0 and Edge E before 8.6.0 allows remote authenticated users to alter WebUI content. The phones store attacker-controlled input in configuration parameters and later render it as webpage content without neutralizing executable markup. Exploitation requires low-privileged configuration access and a user's passive visit to the affected WebUI, and the published impact is content modification rather than disclosure or service interruption.
The record
- CVE
- CVE-2026-5922
- Published
- Jul 8, 2026
- Updated
- Jul 8, 2026
- Vendor
- Plantronics
- Product
- HP Poly Trio C60
- Classifications
- CWE-79
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 8, 2026CVE publishedPublication date reported by the CVE source.
- Jul 8, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <9.5.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo