Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
🐘 Packagist

GHSA-5cmw-fhq9-8fhh

HIGHFix: livehelperchat/livehelperchat@72c0df1

GHSA-5cmw-fhq9-8fhh is a high-severity (CVSS 7.5) CWE-843 vulnerability in remdex/livehelperchat. 1 public exploit reference exists, so weaponization risk is real. O3 Security confirms whether GHSA-5cmw-fhq9-8fhh is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Type Confusion in LiveHelperChat

Also known asBIT-livehelperchat-2022-1176CVE-2022-1176
Published
Apr 1, 2022
Updated
Dec 6, 2023
Affected
1 pkg
Patched
1 / 1
Exploits
1 known

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

Live Helper Chat provides live support for your website. Loose comparison causes IDOR on multiple endpoints in LiveHelperChat prior to 3.96. There is a fix released in versions 3.96 and 3.97. Currently, there is no known workaround.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
🐘Packagistremdex/livehelperchatall versions3.96
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.

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. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  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-5cmw-fhq9-8fhh 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.

  4. How O3 protects you

    O3 pinpoints whether GHSA-5cmw-fhq9-8fhh is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-5cmw-fhq9-8fhh. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

Live Helper Chat provides live support for your website. Loose comparison causes IDOR on multiple endpoints in LiveHelperChat prior to 3.96. There is a fix released in versions 3.96 and 3.97. Currently, there is no known workaround.
O3 Security · Impact-Aware SCA

Is GHSA-5cmw-fhq9-8fhh in your dependencies?

O3 detects GHSA-5cmw-fhq9-8fhh across Packagist dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.