CVE-2026-31889
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 · uneditedShopware is an open commerce platform. Prior to 6.6.10.15 and 6.7.8.1, a vulnerability in the Shopware app registration flow that could, under specific conditions, allow attackers to take over the communication channel between a shop and an app. The legacy app registration flow used HMAC‑based authentication without sufficiently binding a shop installation to its original domain. During re‑registration, the shop-url could be updated without proving control over the previously registered shop or domain. This made targeted hijacking of app communication feasible if an attacker possessed the relevant app‑side secret. By abusing app re‑registration, an attacker could redirect app traffic to an attacker‑controlled domain and potentially obtain API credentials intended for the legitimate shop. This vulnerability is fixed in 6.6.10.15 and 6.7.8.1.
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 confidenceShopware's legacy app registration flow uses HMAC-based authentication without properly binding a shop installation to its original domain. During re-registration, the shop-url can be updated without proving control over the previously registered domain, allowing attackers to hijack app communication channels and potentially obtain API credentials intended for legitimate shops.
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< 6.6.10.15>= 6.7.0.0, < 6.7.8.1CVSS 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
- High
- Privileges
- None
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- Low
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:L
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 checksWork through these to decide whether this CVE applies to you.
-
Check installed Shopware versionNavigate to Shopware admin panel, go to Settings > System > Info, or inspect the composer.lock file in the Shopware root directory to find the installed version numberAffected if Version is below 6.6.10.15 or between 6.7.0.0 and 6.7.8.1 (inclusive)
-
Identify apps using legacy app systemIn Shopware admin, go to Apps > Overview. Legacy apps typically appear with older integration patterns and may not use the modern manifest.xml format. Check the database table app_extension for apps with legacy_app = 1 or similar legacy indicatorsAffected if Any apps are installed using the legacy registration flow on an affected Shopware version
-
Review app registration for shop-url changesQuery the app database tables (such as app_repo or app_sales_channel) to compare current shop-url values against historical registration records. Look for any domain values that differ from the original registrationAffected if Any app shows a shop-url that differs from its original registered domain without documented re-verification
-
Audit app API credential distributionCheck the app_system_config table or equivalent storage for API credentials assigned to apps. Verify that credentials were only issued to the originally registered domain and not redirected to alternative domainsAffected if API credentials for any app were delivered to a domain other than the one originally registered
Environment is affected if running an affected Shopware version and any apps were registered or re-registered through the legacy app system, particularly if domain changes occurred during re-registration.
Generated from the published advisory. Verify against your own configuration.
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 · scoped6.6.10.156.7.8.1
Upgrade Shopware to version 6.6.10.15 or 6.7.8.1 or later. Review existing app registrations and audit for any suspicious domain changes.
Upgrade to Shopware 6.6.10.15 (for 6.6.x branch) or 6.7.8.1 (for 6.7.x branch), or later versions
- 1. Identify the current Shopware version by checking the shop's composer.json or administration interface
- 2. If running version 6.6.x below 6.6.10.15, plan upgrade to 6.6.10.15 or later in the 6.6.x line
- 3. If running version 6.7.x below 6.7.8.1, plan upgrade to 6.7.8.1 or later in the 6.7.x line
- 4. Create a complete backup of the database and all shop files before proceeding
- 5. Run the Shopware composer update command or use the Shopware updater to upgrade to the target version
- 6. Clear all caches after upgrade (bin/console cache:clear)
- 7. Verify the upgrade was successful by checking the Shopware version
- 8. Test the app registration flow to confirm the vulnerability is mitigated
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,728.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-31889 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-31889 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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