SupercheckoutPrestaShop extension · Knowband

CVE-2023-45384

CRITICAL · 9.8 CVSS v3.1 Published 2023-10-19
Fix available
A fix is available. Upgrade to 6.0.7 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
KnowBand supercheckout > 5.0.7 and < 6.0.7 is vulnerable to Unrestricted Upload of File with Dangerous Type. In the module "Module One Page Checkout, Social Login & Mailchimp" (supercheckout), a guest can upload files with extensions .php

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 KnowBand supercheckout module for PrestaShop/ Magento allows guest users to upload files without proper validation, specifically permitting dangerous .php file extensions. This unrestricted file upload vulnerability could allow remote code execution if the uploaded PHP files are accessible and executed by the web server.

MitigationUpgrade to supercheckout version 6.0.7 or later which includes proper file type validation. Until then, disable guest file upload functionality in the module settings or restrict write permissions on the upload directory.

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
SupercheckoutPrestaShop extension
Affected:>= 5.0.7, < 6.0.7

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 KnowBand Supercheckout module is installed
    Check the installed modules list in PrestaShop or Magento admin panel, or inspect the modules directory for 'supercheckout' folder
    Affected if The module is present in the installation
  2. Determine the installed Supercheckout version
    Access the module configuration page in the admin panel to view version info, or inspect the module's main PHP file for a version constant
    Affected if Version is >= 5.0.7 and < 6.0.7
  3. Check if guest file upload is enabled
    Navigate to Supercheckout module settings in admin panel, look for guest checkout or file upload configuration options
    Affected if Guest file upload functionality is enabled in module settings
  4. Inspect the file upload directory
    Locate the upload directory used by Supercheckout (typically /upload/ or /media/ within the module directory) and verify it is web-accessible
    Affected if The upload directory exists and is accessible via HTTP
  5. Verify if .php files can be uploaded
    Attempt a test upload via the guest checkout file upload feature using a harmless test file with .php extension, or review module code for file extension validation logic
    Affected if The module accepts .php file extensions without proper validation

You are affected if the KnowBand Supercheckout module is installed with version >= 5.0.7 and < 6.0.7, and guest file upload is enabled in the module settings.

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

Upgrade to supercheckout version 6.0.7 or later which includes proper file type validation. Until then, disable guest file upload functionality in the module settings or restrict write permissions on the upload directory.

Recommended fix High confidence

Supercheckout 6.0.7 or later

  1. Upgrade the Supercheckout module from the current installed version to version 6.0.7 or later

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

Fix this in Supercheckout Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-45384 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