CVE-2022-0245 json
Cross-Site Request Forgery (CSRF) in livehelperchat/livehelperchat
published 4y ago modified 4mo ago also GHSA-vxh4-x6gv-mphf , EUVD-2022-0710
- cvss
- 5.7
- 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 38%
- public exploits
- 0
- none known
Summary
Cross-Site Request Forgery (CSRF) in GitHub repository livehelperchat/livehelperchat prior to 2.0.
Patch / fix
- livehelperchat livehelperchat/livehelperchat 2.0
Is CVE-2022-0245 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerExploit prediction
0.44% chance of exploitation in the next 30 days, higher than 38% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- huntr.dev https://huntr.dev/bounties/6a6aca72-32b7-45b3-a8ba-9b400b2d669c referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.0 | 5.7 | CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:H/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 |
| GitHub | 3.1 | 4.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| packagist | livehelperchat/livehelperchat | <=3.91 |
no fix listed |
Affected products
- livehelperchat livehelperchat/livehelperchat
Classification
- Weakness
-
- CWE-352 Cross-Site Request Forgery
References
-
github.com
/livehelperchat/livehelperchat/commit/c2fa19afeb8b1ea927fea3fd452515c95f289fb9
web, patch, third-party-advisory
-
huntr.dev
/bounties/6a6aca72-32b7-45b3-a8ba-9b400b2d669c
web, exploit, patch, third-party-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2022-0245
advisory
-
github.com
/livehelperchat/livehelperchat
package
Sources
- CVE List CVE-2022-0245
- GitHub Advisory GHSA-vxh4-x6gv-mphf
- NVD CVE-2022-0245
Fencer Intel 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.