dbcve.org
Product DesignerPrestaShop extension · Prestalife

CVE-2024-24302

CRITICAL · 9.8 CVSS v3.1 Published 2024-03-03
Fix available
A fix is available. Upgrade to 1.178.36 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
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.

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 confidence

A critical vulnerability in the Tunis Soft Product Designer module for PrestaShop allows remote attackers to execute arbitrary code, escalate privileges, and obtain sensitive information through the postProcess() method. This suggests a lack of proper input validation and authorization controls in the module's form handling logic.

MitigationUpgrade the productdesigner module to version 1.178.36 or later. If immediate patching is not possible, disable the module or restrict access to its administrative endpoints.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Product DesignerPrestaShop extension
Affected:< 1.178.36

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
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify Product Designer module is installed
    In PrestaShop admin panel, navigate to Modules > Module Manager and search for 'Product Designer' or 'productdesigner'. Alternatively, check the modules directory (modules/productdesigner) for the module files.
    Affected if The Product Designer module by Tunis Soft/Prestalife is present on the system
  2. Determine installed module version
    Access the module configuration page in PrestaShop admin (Modules > Module Manager > Product Designer) and locate the version number displayed, or inspect the module's main PHP file (modules/productdesigner/productdesigner.php) for a version constant or $this->version property.
    Affected if The installed version is lower than 1.178.36 (e.g., 1.178.35, 1.177.x, etc.)
  3. Confirm module is enabled
    In PrestaShop admin panel, check the module status in Modules > Module Manager. The module should show as 'Enabled' or 'Installed' for the vulnerability to be exploitable.
    Affected if The Product Designer module is enabled and actively running on the PrestaShop installation
  4. Check for exposed administrative endpoint
    Inspect if the module's admin controller (typically at /admin123/index.php?controller=AdminProductDesigner or similar) is accessible without proper authentication, or examine the productdesigner.php file for the postProcess() method visibility and access controls.
    Affected if The postProcess() method is accessible without proper admin authorization or input validation controls are missing from the form handling code

A user is affected if the Prestalife Product Designer module is installed, enabled, and running a version lower than 1.178.36 on their PrestaShop instance.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Upgrade available Upgrade to 1.178.36 or later
Fixed in 1.178.36
Interim mitigation

Upgrade the productdesigner module to version 1.178.36 or later. If immediate patching is not possible, disable the module or restrict access to its administrative endpoints.

Recommended fix High confidence

1.178.36

  1. Create a complete backup of your PrestaShop database and all files
  2. Put your site into maintenance mode to prevent user access during the upgrade
  3. Navigate to the PrestaShop admin dashboard > Modules > Module Manager
  4. Locate the 'Product Designer' module by Tunis Soft
  5. If an upgrade option is available, click to upgrade to the latest version
  6. Otherwise, uninstall the current module and then install version 1.178.36 or later
  7. Clear the PrestaShop cache (go to Advanced Parameters > Performance > Clear cache)
  8. Verify the module is installed and functioning correctly in the admin panel
Caveat Review module settings after upgrade as custom configurations may need reapplication; test thoroughly in staging first

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Product Designer Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA2.0 h
8.0 hours of engineering $1,390
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-24302 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-24302 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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