# CVE-2026-44633: Live Helper Chat: REST API chat update accepts arbitrary chat fields across department boundaries

> A REST API flaw allows users to modify chats in unauthorized departments, enabling data tampering and potential code execution via operator-side JavaScript injection.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 May 2026
- **Updated:** 14 May 2026
- **Also known as:** GHSA-hjqq-qmvj-9whm

## What is CVE-2026-44633?

CVE-2026-44633 is a high-severity missing authorization vulnerability in livehelperchat, published on 14 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Live Helper Chat is an open-source application that enables live support websites. In 4.84v, the Live Helper Chat REST API chat update endpoint allows a REST user with lhchat/use to update a chat in a department they cannot read. The endpoint accepts arbitrary chat object fields, so the user can change the chat hash and status and then access or tamper with the chat through visitor/widget paths. The same write primitive can set operation_admin, which is later emitted as operator-side JavaScript.

Weakness: CWE-863 (Incorrect Authorization)

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


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

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

## Is CVE-2026-44633 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-44633 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-44633 is a high-severity missing authorization vulnerability in livehelperchat, published on 14 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-44633 exists.

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

## Sources

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

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