CVE-2022-2039 json
Free Live Chat Support <= 1.0.11 - Cross-Site Request Forgery to Cross-Site Scripting
published 4y ago modified 4mo ago also EUVD-2022-34342
- cvss
- 8.8
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.6%
- EPSS 0.6% chance of exploitation in 30 days, percentile 51%
- public exploits
- 0
- none known
Summary
The Free Live Chat Support plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including 1.0.11. This is due to missing nonce protection on the livesupporti_settings() function found in the ~/livesupporti.php file. This makes it possible for unauthenticated attackers to inject malicious web scripts into the page, granted they can trick a site's administrator into performing an action such as clicking on a link.
Patch / fix
Is CVE-2022-2039 in your stack? 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.65% chance of exploitation in the next 30 days, higher than 51% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 8.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H |
| NVD | 3.1 | 8.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H |
Affected products
- livesupporti Free Live Chat Support
Classification
- Weakness
-
- CWE-352 Cross-Site Request Forgery
- Technology feeds
References
-
plugins.trac.wordpress.org
/browser/livesupporti/trunk/livesupporti.php#L67
patch, third-party-advisory
- wordfence.com /threat-intel/vulnerabilities/id/dfa3efa2-c542-44b9-8039-13e6eac75101?source=cve
- wordpress.org /plugins/livesupporti/#developers
-
wordfence.com
/vulnerability-advisories/#CVE-2022-2039
third-party-advisory
- plugins.trac.wordpress.org /changeset?sfp_email=&sfph_mail=&reponame=&old=2762052%40livesupporti&new=2762052%40livesupporti&sfp_email=&sf
Sources
- CVE List CVE-2022-2039
- NVD CVE-2022-2039
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.