CVE-2024-36679: livechatpro · Code Injection
Affects livechatproSource CVE Database V5
Not known to be exploited · CVSS 10.0 Critical.
Data as of 26 Oct 2026, 12:54 UTC
- EPSS
- 0.6% chance of exploitation in 30 days – higher than 48% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 19 Jun 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Packagistlivechatpropkg:composer/livechatproOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
To mitigate CVE-2024-36679, organizations should immediately audit their use of the Live Chat Pro module and identify affected versions (<=8.4.0). Since no official patches are currently linked, temporary mitigations include disabling or removing the vulnerable module until a fix is released. Restricting web server write permissions to prevent unauthorized PHP file modifications can reduce exploitation risk. Implementing Web Application Firewalls (WAFs) with rules to detect and block suspicious requests targeting the saveTranslations() method or unusual POST requests can provide interim protection. Monitoring web server logs for anomalous activity related to the module is critical for early detection. Organizations should also enforce strict input validation and sanitization practices in custom code and ensure that tokens or authentication mechanisms are unpredictable and securely implemented. Once a vendor patch is available, prompt application of updates is essential. Additionally, conducting regular security assessments and penetration tests focusing on third-party modules can help identify similar risks proactively.
Description
In the module "Module Live Chat Pro (All in One Messaging)" (livechatpro) <=8.4.0, a guest can perform PHP Code injection. Due to a predictable token, the method `Lcp::saveTranslations()` suffer of a white writer that can inject PHP code into a PHP file.