NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
🐘
🐘 Packagist
Not in CISA KEV
HIGH severity

Weak password hash in LiveHelperChatGHSA-vx8v-g3p3-88vg

HIGHFix: livehelperchat/livehelperchat@6538d6d

GHSA-vx8v-g3p3-88vg is a high-severity (CVSS 7.5) CWE-916 vulnerability in remdex/livehelperchat. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for remdex/livehelperchat — see the affected versions and patch details below.

Also known asBIT-livehelperchat-2022-1235CVE-2022-1235
Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
1 known
Exploitation data as of Nov 8, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
0.6%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs47th percentile — riskier than 47% of all scored CVEsHighest risk
0.00%0.35%0.70%1.06%0.1%0.6%May 26Sep 26Nov 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected
🐘remdex/livehelperchat

Real-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

The secrethash, which the application relies for multiple security measures, can be brute-forced. The hash is quite small, with only 10 characters of only hexadecimal, making 16^10 possilibities ( 1.099.511.627.776 ). The SHA1 of the secret can be obtained via a captcha string and brute-forced offline with an GPU.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
🐘Packagistremdex/livehelperchatall versions3.96composer require remdex/livehelperchat:^3.96

Affected Products

1 product · 1 configurations
Application
live helper chatlivehelperchat
< 3.96
range
Exploits & PoCs
1

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

Weak secrethash can be brute-forced in GitHub repository livehelperchat/…

huntr.devNVDApr 2022

Detection & mitigation playbook

Open-source dependency

  1. Detect

    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.

  2. Fix

    Update remdex/livehelperchat to 3.96 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-vx8v-g3p3-88vg is resolved across your whole dependency graph.

  3. 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

The secrethash, which the application relies for multiple security measures, can be brute-forced. The hash is quite small, with only 10 characters of only hexadecimal, making 16^10 possilibities ( 1.099.511.627.776 ). The SHA1 of the secret can be obtained via a captcha string and brute-forced offline with an GPU.
O3 Security · Impact-Aware SCA

Is GHSA-vx8v-g3p3-88vg in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works
Weak password hash in LiveHelperChat (High 7.5)