Skip to main content
VulnerabilityPublished Updated

CVE-2024-34994: channable · SQL Injection

Affects channableSource CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical.

Data as of 26 Oct 2026, 12:29 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 34% 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:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 19 Jun 2024

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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

ProductAffectedFixed in
GitHubfriends-of-presta/channablepkg:github/friends-of-presta/channableOther threatsAffected
  • <=3.2.1
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-34994, organizations should take immediate and specific actions: 1) Monitor official Channable and PrestaShop channels for patches or updates addressing this vulnerability and apply them promptly once available. 2) In the absence of an official patch, implement Web Application Firewall (WAF) rules to detect and block SQL injection patterns targeting the ChannableFeedModuleFrontController::postProcess() endpoint. 3) Conduct thorough input validation and sanitization on all user-supplied data, especially parameters processed by the vulnerable module, to prevent injection of malicious SQL code. 4) Restrict database user permissions to the minimum necessary to limit the impact of potential exploitation. 5) Enable database activity monitoring and alerting to detect anomalous queries indicative of SQL injection attempts. 6) Consider temporarily disabling or removing the Channable module if it is not essential to business operations until a secure version is available. 7) Educate development and security teams about secure coding practices to prevent similar vulnerabilities in custom modules or integrations.

Description

In the module "Channable" (channable) up to version 3.2.1 from Channable for PrestaShop, a guest can perform SQL injection via `ChannableFeedModuleFrontController::postProcess()`.

References

Community reviews

Loading reviews…