dbcve.org
Product DesignerApplication · Prestalife

CVE-2024-26469

HIGH · 8.1 CVSS v3.1 Published 2024-03-03
Fix available
A fix is available. Upgrade to 1.178.36 or later.
See remediation →
87/100
Remediation priority · High
Remotely reachable 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
Server-Side Request Forgery (SSRF) vulnerability in Tunis Soft "Product Designer" (productdesigner) module for PrestaShop before version 1.178.36, allows remote attackers to cause a denial of service (DoS) and escalate privileges via the url parameter in 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 · high confidence

Server-Side Request Forgery (SSRF) vulnerability in Tunis Soft Product Designer module for PrestaShop. The url parameter in the postProcess() method lacks proper validation, allowing remote attackers to make the server perform arbitrary requests, leading to DoS and potential privilege escalation.

MitigationUpdate the productdesigner module to version 1.178.36 or later. Implement strict input validation on the url parameter to restrict requests to trusted origins.

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 DesignerApplication
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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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
    Access the PrestaShop admin panel and navigate to Modules > Module Manager. Search for 'Product Designer' or 'productdesigner' to confirm the module is present on the system.
    Affected if The Product Designer module is not found in the installed modules list, then this CVE does not apply.
  2. Identify installed module version
    In the PrestaShop admin panel under Modules > Module Manager, locate the Product Designer module and view its version number. Alternatively, check the module's main PHP file (typically in /modules/productdesigner/) for a version constant or the config.xml file.
    Affected if The installed version is below 1.178.36, indicating the module is vulnerable to this SSRF flaw.
  3. Confirm module is enabled and accessible
    In the PrestaShop admin panel, verify the Product Designer module status shows as 'Enabled' and is installed. Also check if the frontend controller handling the postProcess() method is accessible (typically via a route like /module/productdesigner/...).
    Affected if The module is enabled and the admin panel or frontend endpoint accepting the url parameter is accessible, the SSRF vulnerability can be exploited.
  4. Inspect the vulnerable code path
    Examine the productdesigner module's controller file containing the postProcess() method. Look for the url parameter handling without proper validation or allowlist filtering.
    Affected if The code shows the url parameter is processed without validation, the system is vulnerable to SSRF attacks.

A system is affected if the Prestalife Product Designer module is installed with a version lower than 1.178.36 and the module is enabled, allowing the url parameter in postProcess() to be processed without proper validation.

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

Update the productdesigner module to version 1.178.36 or later. Implement strict input validation on the url parameter to restrict requests to trusted origins.

Recommended fix High confidence

Product Designer version 1.178.36 or later

  1. 1. Back up your current PrestaShop installation and database before making any changes.
  2. 2. Download the fixed version of the Product Designer module (version 1.178.36 or later) from the official source (Tunis Soft/PrestaShop Addons).
  3. 3. Uninstall the current vulnerable Product Designer module from your PrestaShop admin panel.
  4. 4. Install the updated Product Designer module (version 1.178.36 or later).
  5. 5. Clear PrestaShop cache after the upgrade.
  6. 6. Verify the fix by testing the postProcess() method functionality with the url parameter to ensure the SSRF vulnerability is patched.
Caveat Minor: Review any custom configurations or integrations with the Product Designer module after upgrade as a precaution

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
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,750
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,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-26469 — 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-26469 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