CVE-2025-51397: CVE-2025-51397: A stored cross-site scripting (XSS) vulnerability in the Facebook Chat module of Live Help…
livehelperchat · live helper chat · NVD published 2025-07-22 · posted 2025-07-22 · last modified 2026-06-17
What it is
A stored cross-site scripting (XSS) vulnerability in the Facebook Chat module of Live Helper Chat v4.60 allows attackers to execute arbitrary web scripts or HTML via injecting a crafted payload into the Surname parameter under the Recipient' Lists.
| Weakness | CWE-779 |
|---|---|
| CVSS vector | CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N (source: 134c704f-9b21-4f2e-91b3-4a467353bcc0) |
| ATT&CK tactics | n/a |
Exploitation evidence
First exploit evidence seen: 2025-07-22 (earliest date across the sources below).
Exploited in the wild
No source on this site lists in-the-wild exploitation yet (CISA KEV, VulnCheck KEV).
Public exploit code
Exploit-DB
- EDB-52377: LiveHelperChat 4.61 - Stored Cross Site Scripting (XSS) via Operator Surname (2025-07-22)
GitHub proof-of-concept repositories below quality bar
1 public repositories from 1 accounts, first seen 2025-07-21.
Verify before running: public PoCs can be malicious. Read the code and only run it in an isolated lab. A PoC means exploit code is public, not that this CVE is exploited in the wild.
Sources: Exploit-DB (OffSec) · nomi-sec/PoC-in-GitHub.
No ATT&CK techniques could be mapped or inferred for this CVE yet.
How to fix it
Fixed versions
- livehelperchat live helper chat: versions up to and including 4.61 are affected; check the vendor advisory for the fixed release.
Derived from the NVD CPE configuration (versionEndExcluding / versionEndIncluding). Always confirm with the vendor advisory.
Vendor advisories and patches
Detection Generic guidance
Response checklist Generic guidance
- Inventory: find every instance of the affected product and version (include internet-facing and forgotten ones).
- Patch or mitigate per the vendor advisory; if you cannot patch, remove internet exposure or apply the vendor workaround.
- Assume compromise if the system was exposed before patching: hunt for the indicators in the advisory and review logs back to the disclosure date.
- Rotate credentials and secrets stored on or used by the affected system if compromise cannot be ruled out.