# CVE-2026-5922: Poly Voice – Potential Unauthorized Modification of WebUI using XSS Attack

> Attackers can inject malicious scripts into the WebUI via stored configuration parameters, allowing unauthorized modification of the interface.

- **Severity:** Medium 5.9 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:P/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 8 Jul 2026
- **Updated:** 9 Jul 2026
- **Also known as:** GHSA-gf54-33r5-j829

## What is CVE-2026-5922?

CVE-2026-5922 is a medium-severity cross-site scripting vulnerability in HP Inc. Poly CCX, published on 8 Jul 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

The IP phone might use malicious input stored in configuration parameters and render it as content for the WebUI’s webpage.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

## Which versions are affected by CVE-2026-5922?


## How do I fix CVE-2026-5922?

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

## Is CVE-2026-5922 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-5922 and fix it if it is affected.

What it is: CVE-2026-5922 is a medium-severity cross-site scripting vulnerability in HP Inc. Poly CCX, published on 8 Jul 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-5922 in the wild and no public exploit code.

Affected product: HP Inc. Poly CCX. 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-2026-5922/ (Markdown: https://insights.sbomify.com/CVE-2026-5922/index.md)
```

## Sources

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

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