dbcve.org
ShopwareApplication

CVE-2024-22406

CRITICAL · 9.8 CVSS v3.1 Published 2024-01-16
Fix available
A fix is available. Upgrade to 6.5.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
Shopware is an open headless commerce platform. The Shopware application API contains a search functionality which enables users to search through information stored within their Shopware instance. The searches performed by this function can be aggregated using the parameters in the “aggregations” object. The ‘name’ field in this “aggregations” object is vulnerable SQL-injection and can be exploited using time-based SQL-queries. This issue has been addressed and users are advised to update to Shopware 6.5.7.4. For older versions of 6.1, 6.2, 6.3 and 6.4 corresponding security measures are also available via a plugin. For the full range of functions, we recommend updating to the latest Shopware version.

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

SQL injection vulnerability in Shopware's search API aggregation functionality. The 'name' field in the aggregations object does not properly sanitize user input, allowing time-based SQL injection attacks via crafted API requests.

MitigationUpdate Shopware to version 6.5.7.4 or later. For versions 6.1-6.4, install the corresponding security plugin. The CVSS 9.8 critical rating demands immediate prioritization given the ease of exploitation and potential for complete database compromise.

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
ShopwareApplication
Affected:< 6.5.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 the installed Shopware version
    Access the Shopware admin panel and navigate to 'Configuration > Basic Information' or check the 'composer.json' file in the Shopware root directory for the 'version' field
    Affected if The version is lower than 6.5.7.4 (e.g., 6.1.x, 6.2.x, 6.3.x, 6.4.x)
  2. Verify the Search API endpoint is accessible
    Send a GET request to /api/search/your-entity-type (e.g., /api/search/product) without authentication or with valid API credentials. The endpoint typically requires authentication via API context or sales channel token.
    Affected if The API responds successfully and returns search results
  3. Confirm aggregation functionality is enabled
    Send a POST request to the search API endpoint with an 'aggregations' object containing a 'name' field, for example: {"aggregations":[{"name":"test_aggregation","field":"product.id"}]}
    Affected if The response includes aggregation results without error, indicating the feature processes the 'name' parameter
  4. Check API access controls
    Review the Shopware API configuration in the admin panel under 'Settings > API' and verify which authentication methods (sales channel API, admin API, or OAuth) are enabled and accessible
    Affected if Any API authentication method is active and allows external requests to the search endpoint

The environment is affected if Shopware version is below 6.5.7.4 and the Search API aggregation endpoint is accessible, as the 'name' field in the aggregations object will process 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 6.5.7.4 or later
Fixed in 6.5.7.4
Interim mitigation

Update Shopware to version 6.5.7.4 or later. For versions 6.1-6.4, install the corresponding security plugin. The CVSS 9.8 critical rating demands immediate prioritization given the ease of exploitation and potential for complete database compromise.

Recommended fix High confidence

Shopware 6.5.7.4

  1. Create a complete backup of the Shopware database and all application files
  2. Verify the current Shopware version is below 6.5.7.4 before proceeding
  3. Update Shopware to version 6.5.7.4 using the official update mechanism (either via the administration panel or command line: bin/console system:update:finish or the updater plugin)
  4. After updating, clear the Shopware cache (bin/console cache:clear)
  5. Verify the update was successful by checking the Shopware version in the administration panel
  6. For Shopware 6.1, 6.2, 6.3, and 6.4 versions that cannot upgrade to 6.5, install the corresponding security plugin provided by Shopware if available
Caveat None explicitly mentioned in the advisory; always review release notes for your specific version jump

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

Fix this in Shopware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
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,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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