CVE-2023-46352
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 · uneditedIn the module "Pixel Plus: Events + CAPI + Pixel Catalog for Facebook Module" (facebookconversiontrackingplus) up to version 2.4.9 from Smart Modules 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 table such as name / surname / email.
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 confidenceThe facebookconversiontrackingplus PrestaShop module up to v2.4.9 lacks authorization checks on export endpoints, allowing unauthenticated guest users to directly access and download customer data exports from the ps_customer table containing names, surnames, and email addresses.
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< 2.4.9CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Check if Facebook Conversion Tracking Plus module is installedAccess PrestaShop back office, navigate to Modules > Module Manager, and search for 'facebookconversiontrackingplus' or 'Facebook Conversion Tracking Plus' to confirm installation statusAffected if The module is listed as installed in the PrestaShop module manager
-
Determine installed version of the moduleIn PrestaShop back office Modules > Module Manager, click on the Facebook Conversion Tracking Plus module to view its version numberAffected if The installed version is less than 2.4.9 (e.g., 2.4.8, 2.4.7, etc.)
-
Inspect export endpoint accessibilityUse a web browser or curl to attempt direct access to the module's export URL without providing any authentication credentials. Common export endpoints may follow patterns like /modules/facebookconversiontrackingplus/export.php or /modules/facebookconversiontrackingplus/controllers/admin/Affected if The export functionality returns customer data (names, surnames, email addresses from ps_customer table) without requiring login or authentication token
User is affected if the Facebook Conversion Tracking Plus module version is below 2.4.9 AND the export endpoints are reachable without authentication, allowing access to customer PII data.
Generated from the published advisory. Verify against your own configuration.
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 · scoped2.4.9
Implement proper authentication and role-based authorization checks on all export functionality to ensure only authenticated users with appropriate permissions can access customer data exports.
Latest version available on addons.prestashop.com (version > 2.4.9)
- Log in to the PrestaShop back office.
- Navigate to Modules > Module Manager.
- Search for the module 'Pixel Plus: Events + CAPI + Pixel Catalog for Facebook' (facebookconversiontrackingplus).
- Check for an update and upgrade to the latest version available (ensure the version is greater than 2.4.9).
- If no update is available via the manager, download the latest version from addons.prestashop.com and upload it via the 'Upload a module' button or via FTP.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-46352 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-46352 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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