dbcve.org
Orders \(csv\, Excel\) Export ProPrestaShop extension · Myprestamodules

CVE-2023-46354

HIGH · 7.5 CVSS v3.1 Published 2023-12-06
Fix available
A fix is available. Upgrade to 5.2.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 "Orders (CSV, Excel) Export PRO" (ordersexport) < 5.2.0 from MyPrestaModules for PrestaShop, a guest can download personal information without restriction. Due to a lack of permissions control, a guest can access exports from the module which can lead to a leak of personal information from ps_customer/ps_address tables such as name / surname / email / phone number / full postal address.

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

The Orders Export PRO module for PrestaShop lacks proper access control checks on its export endpoints, allowing any unauthenticated guest user to directly access and download CSV/Excel exports containing customer PII (names, emails, phone numbers, postal addresses) from the ps_customer and ps_address database tables.

MitigationUpgrade the ordersexport module to version 5.2.0 or later which implements proper permission/authorization checks. Alternatively, restrict access to export URLs at the web server level (e.g., via IP allowlisting or HTTP Basic Auth).

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
Orders \(csv\, Excel\) Export ProPrestaShop extension
Affected:< 5.2.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. Locate the Orders Export PRO module in your PrestaShop installation
    Check the modules directory (usually /modules/) for a folder named 'ordersexport', 'ordersexportpro', or similar containing 'orders' and 'export' in the name. Also check via PrestaShop admin: Modules > Module Manager and search for 'Orders Export' or 'ordersexport'.
    Affected if The module folder or entry exists in your PrestaShop modules directory or appears in the admin module list.
  2. Determine the installed version of the Orders Export module
    Open the main module PHP file (usually /modules/ordersexport/ordersexport.php or /modules/ordersexportpro/ordersexportpro.php) and look for a version variable or constant near the top, such as 'VERSION', '$version', or '$this->version'. Alternatively, check the module's config.xml or composer.json if present.
    Affected if The version number found is lower than 5.2.0 (e.g., 5.1.x, 5.0.x, 4.x, etc.).
  3. Verify if the module is enabled on the store
    In PrestaShop admin, go to Modules > Module Manager, find the Orders Export module, and confirm the status shows as 'Enabled' or 'Installed'. Check the database table ps_module where name LIKE '%ordersexport%' and confirm the active column equals 1.
    Affected if The module is installed and enabled (active = 1).
  4. Identify accessible export endpoint URLs
    Search the module PHP files for patterns like 'export', 'csv', 'excel', 'download', or 'process' within function names or route definitions. Look for any publicly accessible controller files in /modules/ordersexport/controllers/front/ or similar paths. Common URL patterns may include /module/ordersexport/export, /module/ordersexport/download, or /index.php?controller=ordersexport.
    Affected if The module contains export functionality accessible via URL controllers in the front-end.
  5. Test for unauthenticated access to export URLs
    Using a browser or HTTP tool (curl, Burp), attempt to access the identified export URLs without logging in or providing any session token. For example: curl -I https://yourdomain.com/module/ordersexport/export. Check if the request returns a valid CSV/Excel file download or HTTP 200 instead of redirecting to login (HTTP 302 to authenticate) or returning HTTP 403.
    Affected if The export endpoint returns a successful HTTP 200 response with file content (CSV/Excel) without requiring authentication, showing customer data.

Your store is affected if the Orders Export PRO module is installed, enabled, and its export endpoints are reachable without any login or authorization, allowing guest users to download files containing customer PII.

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.2.0 or later
Fixed in 5.2.0
Interim mitigation

Upgrade the ordersexport module to version 5.2.0 or later which implements proper permission/authorization checks. Alternatively, restrict access to export URLs at the web server level (e.g., via IP allowlisting or HTTP Basic Auth).

Recommended fix High confidence

5.2.0

  1. Backup your PrestaShop site and database before making any changes
  2. Download Orders (CSV, Excel) Export PRO version 5.2.0 or later from MyPrestaModules
  3. Install the updated module version through PrestaShop's admin panel or via file upload
  4. Clear PrestaShop cache (in Advanced Parameters > Performance > Clear cache)
  5. Verify the fix by confirming that guest users can no longer access exports without authentication

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

Fix this in Orders \(csv\, Excel\) Export Pro Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.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-2023-46354 — 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-46354 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