dbcve.org
Incorrect AuthorizationWeakness · CWE-863

CVE-2026-44633

HIGH · 8.1 CVSS v3.1 Published 2026-05-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
87/100
Remediation priority · High
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

In Live Helper Chat 4.84v, the REST API chat update endpoint permits a REST user with lhchat/use permission to update chats in departments they lack read access to. The endpoint accepts arbitrary chat object fields, enabling manipulation of chat hash/status to access/tamper with chats via visitor/widget paths, and can set operation_admin which gets rendered as operator-side JavaScript, creating a stored XSS risk.

MitigationImplement strict department-level authorization checks ensuring users can only modify chats in departments they have explicit read/write permissions for, and sanitize or block the operation_admin field from being reflected as executable JavaScript.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify Live Helper Chat installation and version
    Locate the version file (typically version.php or similar in the installation root) or access the admin panel's 'System information' page. Compare the installed version against 4.84v.
    Affected if The installed version is 4.84v or earlier in the 4.x branch.
  2. Confirm REST API endpoint accessibility
    Verify the endpoint /index.php (rest_api)/lhchat/use exists and is reachable. Check the router configuration or .htaccess for route registration of 'lhchat/use'.
    Affected if The endpoint responds to HTTP requests and accepts JSON payloads.
  3. Inspect department authorization logic
    Examine the chat update controller (typically in src/handlers/lhchat or similar) for department permission checks before processing updates. Look for code that validates user department read permissions against the chat's assigned department.
    Affected if No department-level authorization check exists before allowing chat modifications.
  4. Detect arbitrary field acceptance in API
    Send a test request to the chat update endpoint with a field outside the expected set (e.g., an extra 'chat_hash' parameter) and inspect whether the API accepts and processes it.
    Affected if The API accepts and persists fields that are not explicitly defined in the request schema.
  5. Check for operation_admin in JavaScript output
    Locate where operation_admin is emitted in operator-side templates or API responses. Inspect the rendered page source or API response for 'operation_admin' appearing in script tags or event handlers without encoding.
    Affected if The operation_admin value is output directly into JavaScript context without sanitization.

A user is affected if running Live Helper Chat version 4.84v with the REST API endpoint enabled and no additional authorization layer blocks department-crossing chat updates or sanitizes operation_admin before JavaScript emission.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement strict department-level authorization checks ensuring users can only modify chats in departments they have explicit read/write permissions for, and sanitize or block the operation_admin field from being reflected as executable JavaScript.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-44633 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-44633 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data