dbcve.org
Product DesignerPrestaShop extension · Prestalife

CVE-2024-24307

HIGH · 7.5 CVSS v3.1 Published 2024-03-03
Fix available
A fix is available. Upgrade to 1.178.36 or later.
See remediation →
84/100
Remediation priority · High
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
Path Traversal vulnerability in Tunis Soft "Product Designer" (productdesigner) module for PrestaShop before version 1.178.36, allows a remote attacker to escalate privileges and obtain sensitive information via the ajaxProcessCropImage() 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 path traversal vulnerability in the ajaxProcessCropImage() method of the Tunis Soft Product Designer module for PrestaShop allows remote attackers to manipulate file paths using directory traversal sequences (e.g., ../../), enabling unauthorized access to sensitive files outside the intended web directory and potential privilege escalation.

MitigationUpgrade to Product Designer module version 1.178.36 or later. If upgrading is not immediately feasible, implement strict input validation on file path parameters in ajaxProcessCropImage() to reject traversal sequences and whitelist allowed directory paths.

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
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

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. Confirm Product Designer module is installed
    Check your PrestaShop modules directory or access the Modules > Module Manager page to verify the 'Product Designer' or 'Tunis Soft Product Designer' module is present and active
    Affected if The module is installed and active in PrestaShop
  2. Identify the installed Product Designer version
    In PrestaShop admin, go to Modules > Module Manager, find the Product Designer module, and note the displayed version number. Alternatively, check the module's main PHP file for a version constant or the module's config.xml
    Affected if The installed version is lower than 1.178.36
  3. Verify ajaxProcessCropImage endpoint is accessible
    Check if the route or action for ajaxProcessCropImage is exposed in the module's front controller or AJAX processing code. Look for any publicly accessible URL endpoint that calls this method (often in a file like controllers/front/ajax.php or similar)
    Affected if The ajaxProcessCropImage method is accessible via a public or authenticated web endpoint
  4. Test for directory traversal vulnerability
    If you have access to test the functionality, attempt to send a request to the ajaxProcessCropImage endpoint with a manipulated path parameter containing ../../ sequences (e.g., ../../config/settings.inc.php) to see if the application allows accessing files outside the intended directory
    Affected if The application accepts path traversal sequences and returns content from files outside the designated web directory

You are affected if the Tunis Soft (Prestalife) Product Designer module is installed with a version lower than 1.178.36 and the ajaxProcessCropImage functionality is exposed and accepts unsanitized path parameters.

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 to Product Designer module version 1.178.36 or later. If upgrading is not immediately feasible, implement strict input validation on file path parameters in ajaxProcessCropImage() to reject traversal sequences and whitelist allowed directory paths.

Recommended fix High confidence

Upgrade to Product Designer version 1.178.36 or later

  1. 1. Backup your PrestaShop database and files before making any changes
  2. 2. Navigate to the PrestaShop back office modules management section
  3. 3. Locate the 'Product Designer' module by Tunis Soft
  4. 4. Update the module to version 1.178.36 or later
  5. 5. Verify the update was successful by checking the module version in the modules list
  6. 6. Clear any PrestaShop caches if applicable
  7. 7. Test the ajaxProcessCropImage() functionality to ensure normal operation

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

Fix this in Product Designer Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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