CVE-2024-24302: productdesigner · Deserialization of Untrusted Data
Affects productdesignerSource CVE Database V5
Not known to be exploited · CVSS 9.8 Critical : upgrade to 1.178.36 as a priority.
Data as of 26 Oct 2026, 09:15 UTC
- EPSS
- 0.9% chance of exploitation in 30 days – higher than 60% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 1.178.36
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 3 Mar 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
Upgrade friends-of-presta/productdesigner to 1.178.36.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
GitHubfriends-of-presta/productdesignerpkg:github/friends-of-presta/productdesignerOther 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-24302, organizations should immediately upgrade the Tunis Soft Product Designer module to version 1.178.36 or later once available. If you cannot patch yet, apply the following specific measures: 1) Restrict network access to the PrestaShop administration and product designer endpoints using firewalls or IP whitelisting to limit exposure to trusted sources only. 2) Implement Web Application Firewalls (WAFs) with custom rules to detect and block suspicious payloads targeting the postProcess() method or deserialization attempts. 3) Conduct thorough input validation and sanitization on all data processed by the productdesigner module if custom modifications are possible. 4) Monitor application logs and network traffic for unusual activity indicative of exploitation attempts, such as unexpected POST requests or anomalous code execution patterns. 5) Employ runtime application self-protection (RASP) tools to detect and prevent exploitation in real-time. 6) Regularly back up PrestaShop data and configurations to enable rapid recovery in case of compromise. 7) Educate development and operations teams about the risks of unsafe deserialization and secure coding practices to prevent similar vulnerabilities. These targeted actions go beyond generic advice and focus on the unique aspects of this vulnerability’s exploitation vector.
Description
An issue was discovered in Tunis Soft "Product Designer" (productdesigner) module for PrestaShop before version 1.178.36, allows remote attackers to execute arbitrary code, escalate privileges, and obtain sensitive information via the postProcess() method.