dbcve.org
ShopwareApplication

CVE-2025-30151

HIGH · 7.5 CVSS v3.1 Published 2025-04-08
Fix available
A fix is available. Upgrade to 6.5.8.17 / 6.6.10.3 or later.
See remediation →
84/100
Remediation priority · High
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 commerce platform. It's possible to pass long passwords that leads to Denial Of Service via forms in Storefront forms or Store-API. This vulnerability is fixed in 6.6.10.3 or 6.5.8.17. For older versions of 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

Shopware contains a denial-of-service vulnerability where processing excessively long passwords in Storefront forms or the Store-API can cause the application to become unresponsive or crash. This is a resource exhaustion or inefficient processing issue triggered by malformed input.

MitigationUpdate Shopware to version 6.6.10.3 or 6.5.8.17. For Shopware 6.4, install the corresponding security plugin from the Shopware account.

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.8.17>= 6.6.0.0, < 6.6.10.3= 6.7.0.0

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 Shopware version
    Check the version.php or composer.json file in the Shopware installation directory, or run: bin/console --version
    Affected if The installed version is less than 6.5.8.17, or between 6.6.0.0 and 6.10.3 inclusive, or exactly 6.7.0.0
  2. Confirm Storefront is active
    Check if the Storefront theme and controller are accessible. Visit a storefront page or check storefront configuration in the administration panel
    Affected if Storefront is enabled and accessible to users or API consumers
  3. Verify Store-API endpoint availability
    Check if the Store-API endpoint is publicly accessible by reviewing web server configuration or testing the /store-api endpoint
    Affected if Store-API endpoints are exposed without rate limiting or input length restrictions on password fields
  4. Check for password input length validation
    Inspect HTML forms in the Storefront theme for password fields or review the Store-API request validation configuration. Look for maxlength attributes on password inputs
    Affected if No maxlength attribute or validation is set on password fields in registration or login forms

You are affected if your Shopware version falls within the vulnerable ranges AND the Storefront or Store-API is accessible without proper password input length limits enforced.

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.8.17 / 6.6.10.3 or later
Fixed in 6.5.8.176.6.10.3
Interim mitigation

Update Shopware to version 6.6.10.3 or 6.5.8.17. For Shopware 6.4, install the corresponding security plugin from the Shopware account.

Recommended fix High confidence

Upgrade to Shopware 6.5.8.17 (or latest 6.5.x), 6.6.10.3 (or latest 6.6.x), or the latest 6.7.x release after 6.7.0.0

  1. 1. Create a complete backup of the Shopware database and all files
  2. 2. Enable maintenance mode or take the storefront offline
  3. 3. Update Shopware using the Shopware updater or via Composer (composer update --no-interaction)
  4. 4. After update completion, clear the Shopware cache: bin/console cache:clear
  5. 5. Verify the installed version matches the fixed release: bin/console --version
  6. 6. Test critical storefront form submissions to confirm functionality
  7. 7. Disable maintenance mode and monitor for errors
Caveat Review Shopware release notes for breaking changes between your current version and the target version before upgrading

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

Fix this in Shopware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
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,328.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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