CVE-2024-36679
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedIn 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidencePHP code injection vulnerability in PrestaShop module 'Live Chat Pro (All in One Messaging)' (livechatpro) allows unauthenticated guest attackers to execute arbitrary PHP code via the Lcp::saveTranslations() method. The vulnerability stems from a predictable security token that enables a white writer to inject PHP code directly into a PHP file, leading to complete remote code execution.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify PrestaShop installationCheck for PrestaShop by looking for its typical directory structure (e.g., /var/www/html or similar web root) and configuration files like config/settings.inc.php or the presence of PrestaShop-specific folders like /classes/, /modules/, /controllers/.Affected if PrestaShop is installed and running.
-
Check for livechatpro module installationLook for the livechatpro module directory in the PrestaShop modules folder, typically at /modules/livechatpro/ or /modules/livechat_pro/ within the PrestaShop installation directory.Affected if The livechatpro module directory exists on the server.
-
Determine livechatpro module versionExamine the main module file (e.g., livechatpro.php) or a version.xml/config.xml file within the livechatpro module directory for a version number. Compare against the affected version range (versions <= 8.4.0 are vulnerable).Affected if The installed version is 8.4.0 or lower.
-
Verify if module is enabledCheck the PrestaShop database in the ps_module table for the livechatpro entry, or inspect the module configuration through the PrestaShop admin panel to confirm the module is active.Affected if The livechatpro module is enabled and active.
-
Inspect saveTranslations method exposureLocate the file containing the Lcp::saveTranslations() method within the livechatpro module (typically in a main PHP file like lcp.php or livechatpro.php). Verify if this method handles user input without proper sanitization and if it writes to PHP files.Affected if The saveTranslations() method exists and processes input without authentication or sanitization.
The environment is affected if PrestaShop is running with the livechatpro module installed, enabled, and the version is 8.4.0 or lower, allowing unauthenticated access to the vulnerable saveTranslations() method.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpgrade the livechatpro module to a version newer than 8.4.0. If no patched version is available, immediately disable or remove the module. Alternatively, implement proper token randomization, add authentication checks, and sanitize all input in the saveTranslations() method.
- Consultation3.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-36679 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-36679 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data