dbcve.org
ExportproductsPrestaShop extension · Myprestamodules

CVE-2023-46346

HIGH · 7.5 CVSS v3.1 Published 2023-10-25
Fix available
A fix is available. Upgrade to 5.0.0 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
In the module "Product Catalog (CSV, Excel, XML) Export PRO" (exportproducts) in versions up to 4.1.1 from MyPrestaModules for PrestaShop, a guest can download personal information without restriction by performing a path traversal attack. Due to a lack of permissions control and a lack of control in the path name construction, a guest can perform a path traversal to view all files on the information system.

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

A path traversal vulnerability in the 'Product Catalog (CSV, Excel, XML) Export PRO' module for PrestaShop allows unauthenticated guest users to manipulate file path parameters and access files outside the intended directory. The vulnerability stems from insufficient input validation on path names combined with a complete lack of permission controls, enabling attackers to read personal information and potentially any file on the server.

MitigationImplement strict input validation and path sanitization for all file path parameters, add proper authentication and authorization checks, and restrict file access to the intended export directory. Users should update to version 4.1.2 or later when available, or disable the module until patched.

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
ExportproductsPrestaShop extension
Affected:< 5.0.0

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. Verify the Exportproducts module is installed
    Log into the PrestaShop admin panel and navigate to Modules > Module Manager. Search for 'Product Catalog (CSV, Excel, XML) Export PRO' or 'Exportproducts' to confirm it is installed. Alternatively, check the /modules/ directory for a folder named 'exportproducts' or similar.
    Affected if The module appears in the installed modules list
  2. Determine the installed module version
    In the PrestaShop admin panel, go to the module's configuration page and locate the version number displayed in the module information. Compare this version against the affected range of versions prior to 5.0.0.
    Affected if The installed version is lower than 5.0.0
  3. Confirm the module is enabled and active
    In the PrestaShop admin panel under Modules > Module Manager, verify that the Exportproducts module shows as 'Enabled' or 'Installed and enabled' status. Check if the module is hooked to front office controllers.
    Affected if The module is enabled and accessible to visitors
  4. Check for unauthorized access attempts in server logs
    Review web server access logs (typically found in /var/log/apache2/, /var/log/nginx/, or similar) for requests to the module's export functionality containing path traversal patterns such as '../' or '..\' in parameters.
    Affected if Log entries show suspicious requests with '../' patterns targeting export parameters
  5. Inspect module file permissions and configuration
    Examine the module's PHP files in the PrestaShop modules directory, specifically looking for export controllers that handle file path parameters. Verify whether the module implements any input validation or path sanitization on file path parameters.
    Affected if The module accepts path parameters without validation or sanitization

A PrestaShop instance is affected if the Product Catalog Export PRO module from Myprestamodules is installed with a version lower than 5.0.0 and the module is enabled, allowing unauthenticated path traversal access to files outside the export directory.

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 5.0.0 or later
Fixed in 5.0.0
Interim mitigation

Implement strict input validation and path sanitization for all file path parameters, add proper authentication and authorization checks, and restrict file access to the intended export directory. Users should update to version 4.1.2 or later when available, or disable the module until patched.

Recommended fix Moderate confidence

5.0.0 or later

  1. 1. Identify the current version of the 'exportproducts' module installed on your PrestaShop site
  2. 2. Perform a full backup of your PrestaShop database and files before making any changes
  3. 3. Navigate to the PrestaShop Back Office > Modules > Module Manager
  4. 4. Locate the 'Product Catalog (CSV, Excel, XML) Export PRO' (exportproducts) module
  5. 5. Update the module to version 5.0.0 or later if an update is available through the module manager
  6. 6. If the module manager does not show an update, manually upload and install version 5.0.0 or later from MyPrestaModules or an authorized source
  7. 7. Clear the PrestaShop cache after upgrading (Advanced Parameters > Performance > Clear cache)
  8. 8. Verify that the path traversal vulnerability is fixed by attempting to access files outside the intended export directory
Caveat Review the module changelog for version 5.0.0 to check for any configuration changes or new features that may require adjustment

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

Fix this in Exportproducts Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing5.0 h
  • Review / QA3.0 h
17.0 hours of engineering $2,970
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,752.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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