Cross-site Scripting in livehelperchatGHSA-w4hp-pcp8-qhf3
MEDIUMFix: livehelperchat/livehelperchat@ff70c7dGHSA-w4hp-pcp8-qhf3 is a medium-severity (CVSS 5.4) Cross-site Scripting (XSS) vulnerability in remdex/livehelperchat. 1 public exploit reference exists, so weaponization risk is real. A fix is available for remdex/livehelperchat — see the affected versions and patch details below.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
GHSA-w4hp-pcp8-qhf3 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.
Where this sits among everything scored
Of 385,738 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.
Real-World Exposure
remdex/livehelperchatReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.
Description
Stored XSS is found in Settings>Live help configuration>Departments->Departments groups->edit When a user creates a new webhook under the NAME field and puts a payload {{constructor.constructor('alert(1)')()}}, the input gets stored, at user edit groupname , the payload gets executed.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | remdex/livehelperchat | all versions | 3.93composer require remdex/livehelperchat:^3.93 |
Affected Products
livehelperchatlivehelperchatResearch use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for remdex/livehelperchat, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update remdex/livehelperchat to 3.93 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-w4hp-pcp8-qhf3 is resolved across your whole dependency graph.
Workarounds
Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.
Frequently Asked Questions
Is GHSA-w4hp-pcp8-qhf3 in your dependencies?
Find it across Packagist, including transitive dependencies.