dbcve.org
ScquickaccountingPrestaShop extension · Storecommander

CVE-2023-30281

MEDIUM · 6.5 CVSS v3.1 Published 2023-05-16
Fix available
A fix is available. Upgrade to 3.7.3 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable 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
Insecure permissions vulnerability was discovered, due to a lack of permissions’s control in scquickaccounting before v3.7.3 from Store Commander for PrestaShop, a guest can access exports from the module which can lead to leak of personnal informations from ps_customer table sush 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 confidence

The scquickaccounting module before v3.7.3 for PrestaShop lacks proper access control checks on its export functionality. Unauthenticated guest users can directly access export endpoints, allowing them to retrieve sensitive personal data including customer names, surnames, and email addresses from the ps_customer database table.

MitigationUpgrade scquickaccounting module to v3.7.3 or later which includes proper permission controls. Until then, disable or restrict access to the module's export functionality at the web server level.

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
ScquickaccountingPrestaShop extension
Affected:< 3.7.3

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/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. Identify if scquickaccounting module is installed
    Locate the scquickaccounting module directory in your PrestaShop installation, typically under modules/ directory, or check via PrestaShop back office under Modules > Module Manager.
    Affected if The scquickaccounting module is present in the PrestaShop installation.
  2. Check installed module version
    Open the main module file (such as scquickaccounting.php) and locate the version definition, or view the version in PrestaShop back office module details.
    Affected if The installed version is lower than 3.7.3 (e.g., 3.7.2, 3.7.1, 3.6.x, etc.).
  3. Identify export functionality endpoints
    Inspect module files for export-related controllers, functions, or routes - look for keywords such as 'export', 'download', or 'csv' in the module directory structure.
    Affected if Export functionality exists and is accessible within the module.
  4. Test unauthenticated access to export endpoints
    Attempt to access suspected export URLs (e.g., module controller paths) using a browser or curl tool without providing any authentication credentials.
    Affected if The export endpoints return data or valid responses without requiring login or session authentication.
  5. Check for sensitive data exposure in export output
    If export endpoints are accessible, examine any returned data for personal information including customer names, surnames, and email addresses.
    Affected if Export functionality reveals customer PII (names, surnames, email addresses) to unauthenticated users.

You are affected if the scquickaccounting module version is below 3.7.3 AND the export functionality is accessible without authentication, allowing exposure of customer personal data.

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

Upgrade scquickaccounting module to v3.7.3 or later which includes proper permission controls. Until then, disable or restrict access to the module's export functionality at the web server level.

Recommended fix High confidence

3.7.3

  1. Upgrade the Scquickaccounting module from Store Commander to version 3.7.3 or later

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

Fix this in Scquickaccounting Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
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,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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