Skip to main content
CVE-2024-34988VulnerabilityPublished Updated

CVE-2024-34988: n/a

Source CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical.

Data as of 26 Oct 2026, 06:26 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 24 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 2026-10-26.

What to do

AI-suggested

1. Immediate mitigation involves upgrading the affected module to a version that addresses the SQL injection vulnerability once available from the vendor or developer. 2. Until a patch is released, implement web application firewall (WAF) rules specifically designed to detect and block SQL injection attempts targeting the known vulnerable endpoints and parameters. 3. Conduct thorough input validation and sanitization on all user-supplied data within the module's codebase, especially in the affected front controller methods. 4. Restrict database user permissions to the minimum necessary to limit the impact of any successful injection. 5. Monitor logs for unusual database queries or error messages indicative of injection attempts. 6. Employ network segmentation and limit external access to the PrestaShop backend where feasible. 7. Regularly back up databases and test restoration procedures to minimize downtime in case of compromise. 8. Educate development and security teams about secure coding practices to prevent similar vulnerabilities in custom modules.

Description

SQL injection vulnerability in the module "Complete for Create a Quote in Frontend + Backend Pro" (askforaquotemodul) <= 1.0.51 from Buy Addons for PrestaShop allows attackers to view sensitive information and cause other impacts via methods `AskforaquotemodulcustomernewquoteModuleFrontController::run()`, `AskforaquotemoduladdproductnewquoteModuleFrontController::run()`, `AskforaquotemodulCouponcodeModuleFrontController::run()`, `AskforaquotemodulgetshippingcostModuleFrontController::run()`, `AskforaquotemodulgetstateModuleFrontController::run().`

References

Community reviews

Loading reviews…