Is remdex/livehelperchat vulnerable?

Composer remdex/livehelperchat has 23 known advisories in the phpwarden feed. Feed 2026.10.29.1, updated 2026-10-28.

23advisories
0critical
0on CISA KEV
4no fix recorded
CVETitleSeverityCVSSAffectedFixed in
CVE-2024-27516livehelperchat Server-Side Template Injectionmedium0.0<4.294.29
CVE-2022-1176Type Confusion in LiveHelperChathigh7.5<3.963.96
CVE-2022-0266Authorization Bypass Through User-Controlled Key in LiveHelperChatmedium6.5<3.923.92
CVE-2022-0083User enumeration in livehelperchatmedium0.0<3.913.91
CVE-2021-4050Cross site scripting in remdex/livehelperchatmedium6.1<=2.0–
CVE-2022-0253livehelperchat is vulnerable to Cross-site Scriptingmedium5.4<=3.91–
CVE-2022-0370Cross-site Scripting in livehelperchatmedium5.4<3.933.93
CVE-2022-0375Cross-site Scripting in livehelperchatmedium6.5<3.933.93
CVE-2022-0374Cross-site Scripting in livehelperchatmedium6.5<3.933.93
CVE-2021-4132livehelperchat is vulnerable to Cross-site Scriptingmedium5.4<3.913.91
CVE-2022-1530An attacker can execute malicious javascript in Live Helper Chatmedium6.1<3.993.99
CVE-2022-0395Cross-site Scripting in LiveHelperChatmedium5.4<3.933.93
CVE-2022-0387Cross-site Scripting in livehelperchatmedium5.4<3.933.93
CVE-2022-0612Cross-site Scripting in livehelperchatmedium6.7<3.933.93
CVE-2022-0502Cross-site Scripting in LiveHelperChatmedium5.4<3.933.93
CVE-2022-1213Server side request forgery in LiveHelperChathigh7.7<3.673.67
CVE-2021-4131livehelperchat is vulnerable to Cross-Site Request Forgery (CSRF)high8.8<3.913.91
CVE-2022-1235Weak password hash in LiveHelperChathigh7.5<3.963.96
CVE-2022-0394Cross-site Scripting in LiveHelperChatmedium5.4<3.933.93
CVE-2022-0231Cross-Site Request Forgery (CSRF) in livehelperchatmedium6.5<3.923.92
CVE-2021-4123livehelperchat is vulnerable to Cross-Site Request Forgery (CSRF)medium6.5<=3.90–
CVE-2021-4049Cross-Site Request Forgery in remdex/livehelperchatlow0.0<=2.0–
CVE-2022-0226Cross-Site Request Forgery (CSRF) in livehelperchatmedium4.3<3.923.92

Am I affected?

Find out in one command. phpwarden checks your composer.lock against this advisory and 20,000+ others, ranked by real-world exploitation (CISA KEV + EPSS). Free, offline, open data.

# one-time install
pip install phpwarden

# then
phpwarden deps composer.lock

Or keep it checked automatically: GitHub Action · pre-commit hook · GitLab CI · Laravel artisan command

Install docs   How findings are ranked
A version is vulnerable when it falls inside an affected range and below the fixed version. phpwarden applies these ranges to the exact versions in your lockfile or install, so you only see what applies to you.