Cross-Site Request Forgery (CSRF) in livehelperchat
A CSRF issue is found in the audit configuration under settings. It was found that no CSRF token validation is getting done on the server-side. If we remove the CSRF token and keep the CSRF token field empty, the action is getting performed.
Affected software
Click a technology to see all vulnerabilities affecting it.
| Platform | Package | Vulnerable versions | Fixed in |
|---|---|---|---|
| Composer package | remdex/livehelperchat | < 3.92 | 3.92 |
References
- CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N- Weakness (CWE)
CWE-352- Platform
- Composer
- Package
remdex/livehelperchat- Disclosed
- 26.01.2022
- Updated
- 11.10.2026 10:22
Sources and licenses
OSV / GitHub Advisory Database - GHSA-6jmh-9gqm-5xrx - CC BY 4.0
Vulnerability history: remdex/livehelperchat
All published vulnerabilities of this package (Composer package), newest first. Shows whether this is a one-off slip or a package that needs watching.
- Total entries
- 23
- First → latest
- 12.2021 02.2024
- Without a fix
- 4
- Exploited in attacks
- 0
Severity breakdown
- High 4
- Medium 18
- Low 1
Disclosures per year
- 2021: 3
- 2022: 19
- 2023: 0
- 2024: 1
- 2025: 0
- 2026: 0
-
Cross-Site Request Forgery (CSRF) in livehelperchat this entry
Know which vulnerabilities affect your application
With the DockRay integration and software inventory enabled, DockRay checks reported component versions against known vulnerabilities and notifies you about confirmed matches. Coverage depends on the supported technology and available advisory data.