dbcve.org
QuickaccountingPrestaShop extension · Storecommander

CVE-2023-33280

CRITICAL · 9.8 CVSS v3.1 Published 2023-05-25
Fix available
A fix is available. Upgrade to 3.7.4 or later.
See remediation →
100/100
Remediation priority · Urgent
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 Store Commander scquickaccounting module for PrestaShop through 3.7.3, multiple sensitive SQL calls can be executed with a trivial HTTP request and exploited to forge a blind SQL injection.

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 · moderate confidence

A blind SQL injection vulnerability exists in the Store Commander scquickaccounting module for PrestaShop (versions through 3.7.3). The flaw allows unauthenticated attackers to execute arbitrary SQL commands via specially crafted HTTP requests due to improper input sanitization in SQL queries.

MitigationApply the vendor patch or update to a newer version of the scquickaccounting module that addresses the SQL injection. If no patch is available, implement parameterized queries or prepared statements for all database interactions.

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
QuickaccountingPrestaShop extension
Affected:< 3.7.4

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
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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
    Check the PrestaShop modules directory for the scquickaccounting folder. On typical installations, this is located at /modules/scquickaccounting/ or navigate to PrestaShop admin > Modules > Module Manager and search for 'quickaccounting' or 'scquickaccounting'.
    Affected if The scquickaccounting module folder exists in the modules directory or appears in the PrestaShop module list.
  2. Check the installed version of scquickaccounting
    Locate the version information within the module files. Check for a config.xml, info.xml, or the main PHP file (usually scquickaccounting.php) and look for a version definition. Compare the version number against the affected range: versions prior to 3.7.4 are vulnerable.
    Affected if The installed version is lower than 3.7.4 (e.g., 3.7.3, 3.7.2, 3.7.1, etc.).
  3. Verify the module is active
    In PrestaShop admin, go to Module Manager > scquickaccounting and confirm the module status shows as 'Installed' and 'Enabled'. Alternatively, check if the module database tables were created, which indicates the module has been fully installed and activated.
    Affected if The module shows as enabled or installed in the PrestaShop back office.
  4. Check if the vulnerable front controller is accessible
    The SQL injection is exploitable via HTTP requests without authentication. Test if the module's front controller is accessible by attempting to access a URL pattern such as /modules/scquickaccounting/ or checking for publicly accessible PHP files within the module directory that handle HTTP parameters.
    Affected if The module directory is accessible via web and the module accepts user-supplied input through HTTP request parameters without authentication.

You are affected if the scquickaccounting module is installed and enabled with a version lower than 3.7.4, and the module's HTTP endpoints are accessible without authentication.

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.4 or later
Fixed in 3.7.4
Interim mitigation

Apply the vendor patch or update to a newer version of the scquickaccounting module that addresses the SQL injection. If no patch is available, implement parameterized queries or prepared statements for all database interactions.

Recommended fix High confidence

3.7.4

  1. 1. Back up the current scquickaccounting module and the PrestaShop database before making any changes
  2. 2. Download the fixed version (3.7.4) of the scquickaccounting module from the official Store Commander source (www.storecommander.com) or the friends-of-presta advisory for verified patch information
  3. 3. In the PrestaShop admin panel, navigate to the Modules manager and uninstall the current vulnerable scquickaccounting module
  4. 4. Install the new version 3.7.4 of the scquickaccounting module
  5. 5. Clear the PrestaShop cache after the upgrade
  6. 6. Test the module functionality in a staging environment before deploying to production
  7. 7. Deploy the updated module to production

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

Fix this in Quickaccounting Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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