dbcve.org
ShopwareApplication

CVE-2024-22408

HIGH · 8.1 CVSS v3.1 Published 2024-01-16
Fix available
A fix is available. Upgrade to 6.5.7.4 or later.
See remediation →
87/100
Remediation priority · High
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
Shopware is an open headless commerce platform. The implemented Flow Builder functionality in the Shopware application does not adequately validate the URL used when creating the “call webhook” action. This enables malicious users to perform web requests to internal hosts. This issue has been fixed in the Commercial Plugin release 6.5.7.4 or with the Security Plugin. For installations with Shopware 6.4 the Security plugin is recommended to be installed and up to date. For older versions of 6.4 and 6.5 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

Shopware's Flow Builder contains an SSRF vulnerability where the 'call webhook' action does not properly validate URLs, allowing attackers to make requests to internal hosts. This stems from insufficient input validation on the webhook URL parameter.

MitigationApply the vendor patches by updating to Commercial Plugin 6.5.7.4 or later, or install/update the Shopware Security Plugin. For Shopware 6.4 installations, ensure the Security Plugin is current. Alternatively, update to the latest Shopware version.

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/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 installed Shopware version
    Locate the version number in your Shopware installation (typically found in the admin panel under Settings > System > Info, or in a composer.json / shopware.yaml config file)
    Affected if The installed version is lower than 6.5.7.4
  2. Confirm Flow Builder module is active
    Check whether the Flow Builder feature is enabled in your Shopware installation. This may be visible in the admin panel under Automation > Flows, or by checking if the flow_builder table exists in the database
    Affected if Flow Builder is installed and active in the environment
  3. Review configured webhook actions
    Examine any Flow Builder flows that use the 'call webhook' action. This can be done by querying the database for flows containing webhook-related actions, or by reviewing flow configurations in the admin panel
    Affected if Any Flow Builder flow is configured with a webhook action pointing to user-supplied or external URLs
  4. Inspect recent internal HTTP requests
    Review web server logs, application logs, or network traffic for suspicious requests originating from the Shopware server to internal infrastructure (such as internal IPs, localhost, or cloud metadata endpoints)
    Affected if Outbound HTTP requests from the Shopware application target internal/private network addresses

The environment is affected if the installed Shopware version is below 6.5.7.4 and Flow Builder with webhook actions is in use.

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

Apply the vendor patches by updating to Commercial Plugin 6.5.7.4 or later, or install/update the Shopware Security Plugin. For Shopware 6.4 installations, ensure the Security Plugin is current. Alternatively, update to the latest Shopware version.

Recommended fix High confidence

Commercial Plugin 6.5.7.4 (for Shopware 6.5.x); Security Plugin for 6.4.x and earlier

  1. 1. Identify the current Shopware version by checking the Shopware admin panel or composer.json
  2. 2. For Shopware 6.5.x installations: Upgrade the Commercial Plugin to release 6.5.7.4 or later
  3. 3. For Shopware 6.4.x installations: Install or update the Security Plugin to the latest version
  4. 4. For older Shopware versions (pre-6.4): Install the Security Plugin for corresponding security measures
  5. 5. After applying the fix, verify that the Flow Builder webhook action now properly validates URLs and blocks internal host requests
  6. 6. Test the webhook functionality with external URLs to ensure legitimate use cases still work

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
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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