# CVE-2026-0483: Stored Cross-Site Scripting (XSS) vulnerability in LiveHelperChat

> Attackers can execute arbitrary JavaScript in user contexts by uploading malicious PDF files to Live Helper Chat.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:H/VI:N/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:** 28 Jan 2026
- **Updated:** 28 Jan 2026
- **Also known as:** GHSA-g2xg-qw63-fpx3

## What is CVE-2026-0483?

CVE-2026-0483 is a medium-severity cross-site scripting vulnerability in LiveHelperChat, published on 28 Jan 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

Stored Cross-Site Scripting (XSS) vulnerability in the PDF file upload functionality of Live Helper Chat, versions prior to 4.72. An attacker can upload a malicious PDF file containing an XSS payload, which will be executed in the user's context when they download and open the file via the link generated by the application. The vulnerability allows arbitrary JavaScript code to be executed in the user's local context.

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

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


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

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

## Is CVE-2026-0483 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-0483 is a medium-severity cross-site scripting vulnerability in LiveHelperChat, published on 28 Jan 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-0483 in the wild and no public exploit code.

Affected product: LiveHelperChat. 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-0483/ (Markdown: https://insights.sbomify.com/CVE-2026-0483/index.md)
```

## Sources

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

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