CVE-2022-0083 is a high-severity (CVSS 7.3) CWE-209 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.
Generation of Error Message Containing Sensitive Information in livehelperchat/livehelperchat
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
CVE-2022-0083 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
livehelperchat is vulnerable to Generation of Error Message Containing Sensitive Information. There is an observable discrepancy between errors generated for users that exist and those that do not.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | remdex/livehelperchat | all versions | 3.91composer require remdex/livehelperchat:^3.91 |
Affected Products
live helper chatlivehelperchatResearch 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.91 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-0083 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
Frequently Asked Questions
Is CVE-2022-0083 in your dependencies?
Find it across Packagist, including transitive dependencies.