CVE-2022-0226 json
Cross-Site Request Forgery (CSRF) in livehelperchat/livehelperchat
published 2022-01-14 4 y ago modified 2026-06-17 4 mo ago also BIT-livehelperchat-2022-0226 , EUVD-2022-0481 , GHSA-6jmh-9gqm-5xrx
- cvss
- 4.3
- version 3.0, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 39%
- public exploits
- 0
- none known
Summary
livehelperchat is vulnerable to Cross-Site Request Forgery (CSRF)
Patch / fix
- packagist remdex/livehelperchat 3.92
- bitnami livehelperchat 2.0.0
- livehelperchat livehelperchat/livehelperchat 2.0
Exploit prediction
0.45% chance of exploitation in the next 30 days, higher than 39% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- huntr.dev https://huntr.dev/bounties/635d0abf-7680-47f6-a277-d9a91471c73f referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.0 | 4.3 | CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N |
| GitHub | 3.1 | 4.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N |
| NVD | 3.1 | 4.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N |
| NVD | 2.0 | 4.3 | AV:N/AC:M/Au:N/C:N/I:P/A:N |
| OSV | 3.0 | 4.3 | CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| packagist | remdex/livehelperchat | <3.92 |
3.92 |
| bitnami | livehelperchat | <2.0.0 |
2.0.0 |
Affected products
- livehelperchat livehelperchat/livehelperchat
Classification
- Weakness
-
- CWE-352 Cross-Site Request Forgery
References
-
github.com
/livehelperchat/livehelperchat/commit/f59ffb02984c0ce2fbb19ac39365066507de9370
web, patch, third-party-advisory
-
huntr.dev
/bounties/635d0abf-7680-47f6-a277-d9a91471c73f
web, exploit, patch, third-party-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2022-0226
advisory
-
github.com
/livehelperchat/livehelperchat
package
Sources
- CVE List CVE-2022-0226
- GitHub Advisory GHSA-6jmh-9gqm-5xrx
- NVD CVE-2022-0226
- OSV BIT-livehelperchat-2022-0226
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.