ScexportcustomersPrestaShop extension · Prestashop
CVE-2023-30282
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 · uneditedPrestaShop scexportcustomers <= 3.6.1 is vulnerable to Incorrect Access Control. Due to a lack of permissions' control, a guest can access exports from the module which can lead to leak of personal information from customer table.
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 scexportcustomers PrestaShop module versions 3.6.1 and below lacks proper access control checks on its export functionality, allowing unauthenticated guest users to directly access customer data exports and potentially exfiltrate personal information (PII) from the customer database table.
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
ScexportcustomersPrestaShop extension
<= 3.6.1CVSS 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.
-
Identify if the scexportcustomers module is installedCheck the PrestaShop modules directory for the scexportcustomers folder, typically located at /modules/scexportcustomers/ in the PrestaShop installation rootAffected if The scexportcustomers folder exists in the modules directory
-
Determine the installed module versionOpen the main module file (usually scexportcustomers.php) or config.xml within the scexportcustomers module directory and locate the version number defined in the module configurationAffected if The version listed is 3.6.1 or any version lower than 3.6.2
-
Locate the export functionality endpointExamine the module PHP files to identify the controller or script handling the export action, typically named export.php, exportcustomers.php, or similar within the module directoryAffected if An export controller or script exists that processes customer data requests
-
Test unauthenticated access to the export endpointUsing a web browser or HTTP tool, attempt to access the identified export URL without providing any authentication credentials or session cookiesAffected if The export endpoint returns customer data or triggers a download without requiring login or displaying an access denied message
A user is affected if the scexportcustomers module version is 3.6.1 or below AND the export functionality is accessible to unauthenticated users without any login requirement.
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.
From vendor dataUpgrade the scexportcustomers module to version 3.6.2 or later which implements proper permission validation, or if no update is available, implement role-based access control on the export endpoints to ensure only authenticated users with proper privileges can access customer data exports.
Fix this in Scexportcustomers
Scoped from the published advisory
- 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-30282 — 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-30282 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