dbcve.org
ConfiguratorPrestaShop extension · Dmconcept

CVE-2023-43986

CRITICAL · 9.8 CVSS v3.1 Published 2023-10-19
Fix available
A fix is available. Upgrade to 4.9.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
DM Concept configurator before v4.9.4 was discovered to contain a SQL injection vulnerability via the component ConfiguratorAttachment::getAttachmentByToken.

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

SQL injection vulnerability in ConfiguratorAttachment::getAttachmentByToken component of DM Concept configurator versions prior to 4.9.4 allows unauthenticated remote attackers to inject malicious SQL queries via unsanitized input.

MitigationUpgrade DM Concept configurator to v4.9.4 or later to remediate the SQL injection vulnerability. If immediate upgrade is not possible, implement input validation and parameterized queries as compensating controls.

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
ConfiguratorPrestaShop extension
Affected:< 4.9.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 installed DM Concept Configurator version
    Check the version file, admin dashboard, or application headers. Common locations include version.php, a config file, or the system information page within the configurator admin panel.
    Affected if The version is lower than 4.9.4 (e.g., 4.9.3, 4.9.0, or earlier)
  2. Locate the ConfiguratorAttachment component
    Search the application source code for the file containing ConfiguratorAttachment class, typically in a modules or components directory.
    Affected if The ConfiguratorAttachment class file exists and contains the getAttachmentByToken method
  3. Verify getAttachmentByToken method implementation
    Inspect the getAttachmentByToken method in the ConfiguratorAttachment class. Look for direct use of input parameters in SQL queries without parameterization.
    Affected if The method uses raw user input (such as a token parameter) directly in SQL queries without prepared statements or escaping
  4. Check web accessibility of the vulnerable endpoint
    Determine if the getAttachmentByToken functionality is exposed via a web URL or API endpoint accessible without authentication.
    Affected if The endpoint is reachable over HTTP/HTTPS without authentication and accepts a token parameter
  5. Confirm lack of input sanitization
    Review the code handling the token parameter in getAttachmentByToken. Check if there is validation, escaping, or use of parameterized queries before constructing the SQL statement.
    Affected if No input validation, escaping, or parameterized queries are performed on the token parameter before SQL execution

The system is affected if the installed DM Concept Configurator version is below 4.9.4 and the ConfiguratorAttachment::getAttachmentByToken component is accessible without authentication and processes SQL queries with unsanitized input.

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

Upgrade DM Concept configurator to v4.9.4 or later to remediate the SQL injection vulnerability. If immediate upgrade is not possible, implement input validation and parameterized queries as compensating controls.

Recommended fix High confidence

4.9.4

  1. 1. Create a complete backup of your PrestaShop installation and database before proceeding with any changes
  2. 2. Navigate to the PrestaShop Addons marketplace (addons.prestashop.com) and download DM Concept Configurator version 4.9.4 or later
  3. 3. In your PrestaShop admin panel, go to Modules > Module Manager and uninstall the current vulnerable Configurator module
  4. 4. Upload and install the new Configurator version 4.9.4 through PrestaShop's module upload feature or by replacing the module files in /modules/ directory
  5. 5. Clear the PrestaShop cache by navigating to Advanced Parameters > Performance and clicking 'Clear cache'
  6. 6. Verify that the ConfiguratorAttachment::getAttachmentByToken function is no longer vulnerable by testing the affected functionality
  7. 7. Confirm the module version is correctly reported as 4.9.4 or higher in the admin panel

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

Fix this in Configurator Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,780
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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