Vulnerability-Lookup

CVE-2026-31889 (GCVE-0-2026-31889)

Vulnerability from cvelistv5 – Published: 2026-03-11 18:56 – Updated: 2026-03-12 20:04

Title

Shopware has a potential take over of app credentials

Summary

Shopware 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.

Severity ?

8.9 (High)


                        
                          CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:L

CWE

CWE-290 - Authentication Bypass by Spoofing

Assigner

GitHub_M

References

URL

Tags

https://github.com/shopware/shopware/security/adv…

x_refsource_CONFIRM

Impacted products

Vendor

Product

Version

shopware

core

Affected: >= 6.7.0.0, < 6.7.8.1
Affected: < 6.6.10.15

shopware

platform

Affected: >= 6.7.0.0, < 6.7.8.1
Affected: < 6.6.10.15

Show details on NVD website

JSON

To clipboard

{
  "containers": {
    "adp": [
      {
        "metrics": [
          {
            "other": {
              "content": {
                "id": "CVE-2026-31889",
                "options": [
                  {
                    "Exploitation": "none"
                  },
                  {
                    "Automatable": "no"
                  },
                  {
                    "Technical Impact": "total"
                  }
                ],
                "role": "CISA Coordinator",
                "timestamp": "2026-03-12T20:04:03.569165Z",
                "version": "2.0.3"
              },
              "type": "ssvc"
            }
          }
        ],
        "providerMetadata": {
          "dateUpdated": "2026-03-12T20:04:11.623Z",
          "orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
          "shortName": "CISA-ADP"
        },
        "title": "CISA ADP Vulnrichment"
      }
    ],
    "cna": {
      "affected": [
        {
          "product": "core",
          "vendor": "shopware",
          "versions": [
            {
              "status": "affected",
              "version": "\u003e= 6.7.0.0, \u003c 6.7.8.1"
            },
            {
              "status": "affected",
              "version": "\u003c 6.6.10.15"
            }
          ]
        },
        {
          "product": "platform",
          "vendor": "shopware",
          "versions": [
            {
              "status": "affected",
              "version": "\u003e= 6.7.0.0, \u003c 6.7.8.1"
            },
            {
              "status": "affected",
              "version": "\u003c 6.6.10.15"
            }
          ]
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "Shopware 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\u2011based authentication without sufficiently binding a shop installation to its original domain. During re\u2011registration, 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\u2011side secret. By abusing app re\u2011registration, an attacker could redirect app traffic to an attacker\u2011controlled 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."
        }
      ],
      "metrics": [
        {
          "cvssV3_1": {
            "attackComplexity": "HIGH",
            "attackVector": "NETWORK",
            "availabilityImpact": "LOW",
            "baseScore": 8.9,
            "baseSeverity": "HIGH",
            "confidentialityImpact": "HIGH",
            "integrityImpact": "HIGH",
            "privilegesRequired": "NONE",
            "scope": "CHANGED",
            "userInteraction": "NONE",
            "vectorString": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:L",
            "version": "3.1"
          }
        }
      ],
      "problemTypes": [
        {
          "descriptions": [
            {
              "cweId": "CWE-290",
              "description": "CWE-290: Authentication Bypass by Spoofing",
              "lang": "en",
              "type": "CWE"
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-03-11T18:56:23.171Z",
        "orgId": "a0819718-46f1-4df5-94e2-005712e83aaa",
        "shortName": "GitHub_M"
      },
      "references": [
        {
          "name": "https://github.com/shopware/shopware/security/advisories/GHSA-c4p7-rwrg-pf6p",
          "tags": [
            "x_refsource_CONFIRM"
          ],
          "url": "https://github.com/shopware/shopware/security/advisories/GHSA-c4p7-rwrg-pf6p"
        }
      ],
      "source": {
        "advisory": "GHSA-c4p7-rwrg-pf6p",
        "discovery": "UNKNOWN"
      },
      "title": "Shopware has a potential take over of app credentials"
    }
  },
  "cveMetadata": {
    "assignerOrgId": "a0819718-46f1-4df5-94e2-005712e83aaa",
    "assignerShortName": "GitHub_M",
    "cveId": "CVE-2026-31889",
    "datePublished": "2026-03-11T18:56:23.171Z",
    "dateReserved": "2026-03-09T21:59:02.687Z",
    "dateUpdated": "2026-03-12T20:04:11.623Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2",
  "vulnerability-lookup:meta": {
    "nvd": "{\"cve\":{\"id\":\"CVE-2026-31889\",\"sourceIdentifier\":\"security-advisories@github.com\",\"published\":\"2026-03-11T20:16:15.287\",\"lastModified\":\"2026-03-16T20:18:18.410\",\"vulnStatus\":\"Analyzed\",\"cveTags\":[],\"descriptions\":[{\"lang\":\"en\",\"value\":\"Shopware 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\u2011based authentication without sufficiently binding a shop installation to its original domain. During re\u2011registration, 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\u2011side secret. By abusing app re\u2011registration, an attacker could redirect app traffic to an attacker\u2011controlled 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.\"},{\"lang\":\"es\",\"value\":\"Shopware es una plataforma de comercio abierta. Antes de las versiones 6.6.10.15 y 6.7.8.1, una vulnerabilidad en el flujo de registro de aplicaciones de Shopware que podr\u00eda, bajo condiciones espec\u00edficas, permitir a los atacantes tomar el control del canal de comunicaci\u00f3n entre una tienda y una aplicaci\u00f3n. El flujo de registro de aplicaciones heredado utilizaba autenticaci\u00f3n basada en HMAC sin vincular suficientemente una instalaci\u00f3n de tienda a su dominio original. Durante el nuevo registro, la URL de la tienda podr\u00eda actualizarse sin probar el control sobre la tienda o dominio previamente registrado. Esto hizo factible el secuestro dirigido de la comunicaci\u00f3n de la aplicaci\u00f3n si un atacante pose\u00eda el secreto relevante del lado de la aplicaci\u00f3n. Al abusar del nuevo registro de la aplicaci\u00f3n, un atacante podr\u00eda redirigir el tr\u00e1fico de la aplicaci\u00f3n a un dominio controlado por el atacante y potencialmente obtener credenciales de API destinadas a la tienda leg\u00edtima. Esta vulnerabilidad est\u00e1 corregida en las versiones 6.6.10.15 y 6.7.8.1.\"}],\"metrics\":{\"cvssMetricV31\":[{\"source\":\"security-advisories@github.com\",\"type\":\"Secondary\",\"cvssData\":{\"version\":\"3.1\",\"vectorString\":\"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:L\",\"baseScore\":8.9,\"baseSeverity\":\"HIGH\",\"attackVector\":\"NETWORK\",\"attackComplexity\":\"HIGH\",\"privilegesRequired\":\"NONE\",\"userInteraction\":\"NONE\",\"scope\":\"CHANGED\",\"confidentialityImpact\":\"HIGH\",\"integrityImpact\":\"HIGH\",\"availabilityImpact\":\"LOW\"},\"exploitabilityScore\":2.2,\"impactScore\":6.0}]},\"weaknesses\":[{\"source\":\"security-advisories@github.com\",\"type\":\"Primary\",\"description\":[{\"lang\":\"en\",\"value\":\"CWE-290\"}]}],\"configurations\":[{\"nodes\":[{\"operator\":\"OR\",\"negate\":false,\"cpeMatch\":[{\"vulnerable\":true,\"criteria\":\"cpe:2.3:a:shopware:shopware:*:*:*:*:*:*:*:*\",\"versionEndExcluding\":\"6.6.10.15\",\"matchCriteriaId\":\"C5486B22-79CE-4581-BD61-4CF0E3BFB843\"},{\"vulnerable\":true,\"criteria\":\"cpe:2.3:a:shopware:shopware:*:*:*:*:*:*:*:*\",\"versionStartIncluding\":\"6.7.0.0\",\"versionEndExcluding\":\"6.7.8.1\",\"matchCriteriaId\":\"A198E1E6-E6EE-4D98-BF25-E2A5055E8DC8\"}]}]}],\"references\":[{\"url\":\"https://github.com/shopware/shopware/security/advisories/GHSA-c4p7-rwrg-pf6p\",\"source\":\"security-advisories@github.com\",\"tags\":[\"Vendor Advisory\"]}]}}",
    "vulnrichment": {
      "containers": "{\"adp\": [{\"title\": \"CISA ADP Vulnrichment\", \"metrics\": [{\"other\": {\"type\": \"ssvc\", \"content\": {\"id\": \"CVE-2026-31889\", \"role\": \"CISA Coordinator\", \"options\": [{\"Exploitation\": \"none\"}, {\"Automatable\": \"no\"}, {\"Technical Impact\": \"total\"}], \"version\": \"2.0.3\", \"timestamp\": \"2026-03-12T20:04:03.569165Z\"}}}], \"providerMetadata\": {\"orgId\": \"134c704f-9b21-4f2e-91b3-4a467353bcc0\", \"shortName\": \"CISA-ADP\", \"dateUpdated\": \"2026-03-12T20:04:07.189Z\"}}], \"cna\": {\"title\": \"Shopware has a potential take over of app credentials\", \"source\": {\"advisory\": \"GHSA-c4p7-rwrg-pf6p\", \"discovery\": \"UNKNOWN\"}, \"metrics\": [{\"cvssV3_1\": {\"scope\": \"CHANGED\", \"version\": \"3.1\", \"baseScore\": 8.9, \"attackVector\": \"NETWORK\", \"baseSeverity\": \"HIGH\", \"vectorString\": \"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:L\", \"integrityImpact\": \"HIGH\", \"userInteraction\": \"NONE\", \"attackComplexity\": \"HIGH\", \"availabilityImpact\": \"LOW\", \"privilegesRequired\": \"NONE\", \"confidentialityImpact\": \"HIGH\"}}], \"affected\": [{\"vendor\": \"shopware\", \"product\": \"core\", \"versions\": [{\"status\": \"affected\", \"version\": \"\u003e= 6.7.0.0, \u003c 6.7.8.1\"}, {\"status\": \"affected\", \"version\": \"\u003c 6.6.10.15\"}]}, {\"vendor\": \"shopware\", \"product\": \"platform\", \"versions\": [{\"status\": \"affected\", \"version\": \"\u003e= 6.7.0.0, \u003c 6.7.8.1\"}, {\"status\": \"affected\", \"version\": \"\u003c 6.6.10.15\"}]}], \"references\": [{\"url\": \"https://github.com/shopware/shopware/security/advisories/GHSA-c4p7-rwrg-pf6p\", \"name\": \"https://github.com/shopware/shopware/security/advisories/GHSA-c4p7-rwrg-pf6p\", \"tags\": [\"x_refsource_CONFIRM\"]}], \"descriptions\": [{\"lang\": \"en\", \"value\": \"Shopware 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\\u2011based authentication without sufficiently binding a shop installation to its original domain. During re\\u2011registration, 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\\u2011side secret. By abusing app re\\u2011registration, an attacker could redirect app traffic to an attacker\\u2011controlled 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.\"}], \"problemTypes\": [{\"descriptions\": [{\"lang\": \"en\", \"type\": \"CWE\", \"cweId\": \"CWE-290\", \"description\": \"CWE-290: Authentication Bypass by Spoofing\"}]}], \"providerMetadata\": {\"orgId\": \"a0819718-46f1-4df5-94e2-005712e83aaa\", \"shortName\": \"GitHub_M\", \"dateUpdated\": \"2026-03-11T18:56:23.171Z\"}}}",
      "cveMetadata": "{\"cveId\": \"CVE-2026-31889\", \"state\": \"PUBLISHED\", \"dateUpdated\": \"2026-03-12T20:04:11.623Z\", \"dateReserved\": \"2026-03-09T21:59:02.687Z\", \"assignerOrgId\": \"a0819718-46f1-4df5-94e2-005712e83aaa\", \"datePublished\": \"2026-03-11T18:56:23.171Z\", \"assignerShortName\": \"GitHub_M\"}",
      "dataType": "CVE_RECORD",
      "dataVersion": "5.2"
    }
  }
}

FKIE_CVE-2026-31889

Vulnerability from fkie_nvd - Published: 2026-03-11 20:16 - Updated: 2026-03-16 20:18

Severity ?

8.9 (High) - CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:L

Summary

References

	URL	Tags
	security-advisories@github.com	https://github.com/shopware/shopware/security/advisories/GHSA-c4p7-rwrg-pf6p	Vendor Advisory

Impacted products

	Vendor	Product	Version
	shopware	shopware	*
	shopware	shopware	*

JSON

To clipboard

{
  "configurations": [
    {
      "nodes": [
        {
          "cpeMatch": [
            {
              "criteria": "cpe:2.3:a:shopware:shopware:*:*:*:*:*:*:*:*",
              "matchCriteriaId": "C5486B22-79CE-4581-BD61-4CF0E3BFB843",
              "versionEndExcluding": "6.6.10.15",
              "vulnerable": true
            },
            {
              "criteria": "cpe:2.3:a:shopware:shopware:*:*:*:*:*:*:*:*",
              "matchCriteriaId": "A198E1E6-E6EE-4D98-BF25-E2A5055E8DC8",
              "versionEndExcluding": "6.7.8.1",
              "versionStartIncluding": "6.7.0.0",
              "vulnerable": true
            }
          ],
          "negate": false,
          "operator": "OR"
        }
      ]
    }
  ],
  "cveTags": [],
  "descriptions": [
    {
      "lang": "en",
      "value": "Shopware 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\u2011based authentication without sufficiently binding a shop installation to its original domain. During re\u2011registration, 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\u2011side secret. By abusing app re\u2011registration, an attacker could redirect app traffic to an attacker\u2011controlled 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."
    },
    {
      "lang": "es",
      "value": "Shopware es una plataforma de comercio abierta. Antes de las versiones 6.6.10.15 y 6.7.8.1, una vulnerabilidad en el flujo de registro de aplicaciones de Shopware que podr\u00eda, bajo condiciones espec\u00edficas, permitir a los atacantes tomar el control del canal de comunicaci\u00f3n entre una tienda y una aplicaci\u00f3n. El flujo de registro de aplicaciones heredado utilizaba autenticaci\u00f3n basada en HMAC sin vincular suficientemente una instalaci\u00f3n de tienda a su dominio original. Durante el nuevo registro, la URL de la tienda podr\u00eda actualizarse sin probar el control sobre la tienda o dominio previamente registrado. Esto hizo factible el secuestro dirigido de la comunicaci\u00f3n de la aplicaci\u00f3n si un atacante pose\u00eda el secreto relevante del lado de la aplicaci\u00f3n. Al abusar del nuevo registro de la aplicaci\u00f3n, un atacante podr\u00eda redirigir el tr\u00e1fico de la aplicaci\u00f3n a un dominio controlado por el atacante y potencialmente obtener credenciales de API destinadas a la tienda leg\u00edtima. Esta vulnerabilidad est\u00e1 corregida en las versiones 6.6.10.15 y 6.7.8.1."
    }
  ],
  "id": "CVE-2026-31889",
  "lastModified": "2026-03-16T20:18:18.410",
  "metrics": {
    "cvssMetricV31": [
      {
        "cvssData": {
          "attackComplexity": "HIGH",
          "attackVector": "NETWORK",
          "availabilityImpact": "LOW",
          "baseScore": 8.9,
          "baseSeverity": "HIGH",
          "confidentialityImpact": "HIGH",
          "integrityImpact": "HIGH",
          "privilegesRequired": "NONE",
          "scope": "CHANGED",
          "userInteraction": "NONE",
          "vectorString": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:L",
          "version": "3.1"
        },
        "exploitabilityScore": 2.2,
        "impactScore": 6.0,
        "source": "security-advisories@github.com",
        "type": "Secondary"
      }
    ]
  },
  "published": "2026-03-11T20:16:15.287",
  "references": [
    {
      "source": "security-advisories@github.com",
      "tags": [
        "Vendor Advisory"
      ],
      "url": "https://github.com/shopware/shopware/security/advisories/GHSA-c4p7-rwrg-pf6p"
    }
  ],
  "sourceIdentifier": "security-advisories@github.com",
  "vulnStatus": "Analyzed",
  "weaknesses": [
    {
      "description": [
        {
          "lang": "en",
          "value": "CWE-290"
        }
      ],
      "source": "security-advisories@github.com",
      "type": "Primary"
    }
  ]
}

GHSA-C4P7-RWRG-PF6P

Vulnerability from github – Published: 2026-03-11 19:24 – Updated: 2026-03-11 21:37

Summary

Shopware vulnerable to a potential take over of app credentials

Details

Summary

We identified and fixed 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. 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. We have no evidence that this vulnerability has been exploited.

Affected Scope

All apps (public and private) that use a registrationUrl in their app manifest and rely on the legacy HMAC‑based registration flow.
Both on‑premise and cloud installations are affected until updated to a fixed Shopware version or protected by the latest Shopware Security Plugin.
Shopware services and first‑party apps using the affected SDKs were reviewed and patched. The vulnerability does not affect core storefront or administration authentication; it is limited to the app system’s registration and re‑registration mechanism.

Impact

In a successful attack, an attacker who already knows certain app‑side secrets could: - Re‑register an existing app installation with a domain under their control. - Intercept App → Shop communication and cause data tampering (“data poisoning”). - Obtain API integration credentials of the shop with the permissions granted to the app. Shop owners and app manufacturers would typically observe this as “app malfunction” rather than an obvious security issue, which increases the need for hardening.

Root Cause

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.

Fix

We have hardened the app registration and re‑registration process: - Dual signature requirement: Re‑registration now requires both the app secret and the existing shop secret to be presented and validated. - Mandatory secret rotation: On successful re‑registration, a new shop secret is generated and verified; the previous secret is invalidated after a short grace period. - Stricter validation: Shopware only accepts updated shop URLs and secrets once the full confirmation flow has completed successfully. - Improved logging and monitoring: All re‑registrations are now logged with additional metadata to help detect abuse patterns. These changes are delivered via: - Updated Shopware core releases (6.6.x, 6.7.x), and - Updated versions of the Shopware Security Plugin for supported older versions, - Updated official SDKs (e.g. PHP and JavaScript app SDKs).

Required Action

For Merchants / Shop Operators

Update Shopware
Upgrade to the latest Shopware 6.6.x / 6.7.x release that includes this fix, or
Install/update the latest Shopware Security Plugin version providing the hotfix for your Shopware 6 installation.
Update apps
Ensure all installed apps are updated to the latest versions provided by their manufacturers.
If you suspect compromised keys or observe unexpected app behaviour, re‑install the affected app or trigger key rotation as documented by the app vendor.

For App Manufacturers / Partners

Update SDKs / implementations
Update to the latest Shopware app SDKs (PHP / JS) or apply the documented changes if you maintain a custom implementation of the registration flow.
Validate both shopware-app-signature and shopware-shop-signature for re‑registration requests.
Always generate and store a new shop secret on re‑registration and only switch to it after a successful confirmation.
Review your apps
Verify that your app does not blindly accept changed shop-url values without validating signatures.
Check any logic that exposes data or functionality based solely on HMAC signatures from shops and ensure it aligns with the hardened registration model.
Test your implementation
Use the updated tooling and guidance provided in your Shopware Account / partner channels to validate that your registration flow complies with the new requirements.

Severity ?

8.9 (High)


                  
                    CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:L

Show details on source website

JSON

To clipboard

{
  "affected": [
    {
      "package": {
        "ecosystem": "Packagist",
        "name": "shopware/platform"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "6.7.0.0"
            },
            {
              "fixed": "6.7.8.1"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    },
    {
      "package": {
        "ecosystem": "Packagist",
        "name": "shopware/platform"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "6.6.10.15"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    },
    {
      "package": {
        "ecosystem": "Packagist",
        "name": "shopware/core"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "6.7.0.0"
            },
            {
              "fixed": "6.7.8.1"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    },
    {
      "package": {
        "ecosystem": "Packagist",
        "name": "shopware/core"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "6.6.10.15"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "aliases": [
    "CVE-2026-31889"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-290"
    ],
    "github_reviewed": true,
    "github_reviewed_at": "2026-03-11T19:24:06Z",
    "nvd_published_at": "2026-03-11T20:16:15Z",
    "severity": "HIGH"
  },
  "details": "### Summary\n\nWe identified and fixed 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. By abusing app re\u2011registration, an attacker could redirect app traffic to an attacker\u2011controlled domain and potentially obtain API credentials intended for the legitimate shop.\nWe have no evidence that this vulnerability has been exploited.\n\n---\n\n### Affected Scope\n\n- All apps (public and private) that use a `registrationUrl` in their app manifest and rely on the legacy HMAC\u2011based registration flow.\n- Both on\u2011premise and cloud installations are affected until updated to a fixed Shopware version or protected by the latest Shopware Security Plugin.\n- Shopware services and first\u2011party apps using the affected SDKs were reviewed and patched.\nThe vulnerability does not affect core storefront or administration authentication; it is limited to the app system\u2019s registration and re\u2011registration mechanism.\n\n---\n\n### Impact\n\nIn a successful attack, an attacker who already knows certain app\u2011side secrets could:\n- Re\u2011register an existing app installation with a domain under their control.\n- Intercept App \u2192 Shop communication and cause data tampering (\u201cdata poisoning\u201d).\n- Obtain API integration credentials of the shop with the permissions granted to the app.\nShop owners and app manufacturers would typically observe this as \u201capp malfunction\u201d rather than an obvious security issue, which increases the need for hardening.\n\n---\n\n### Root Cause\n\nThe legacy app registration flow used HMAC\u2011based authentication without sufficiently binding a shop installation to its original domain. During re\u2011registration, 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\u2011side secret.\n\n---\n\n### Fix\n\nWe have hardened the app registration and re\u2011registration process:\n- **Dual signature requirement:** Re\u2011registration now requires both the app secret and the existing shop secret to be presented and validated.\n- **Mandatory secret rotation:** On successful re\u2011registration, a new shop secret is generated and verified; the previous secret is invalidated after a short grace period.\n- **Stricter validation:** Shopware only accepts updated shop URLs and secrets once the full confirmation flow has completed successfully.\n- **Improved logging and monitoring:** All re\u2011registrations are now logged with additional metadata to help detect abuse patterns.\nThese changes are delivered via:\n- Updated Shopware core releases (6.6.x, 6.7.x), and\n- Updated versions of the Shopware Security Plugin for supported older versions,\n- Updated official SDKs (e.g. PHP and JavaScript app SDKs).\n---\n\n### Required Action\n\n#### For Merchants / Shop Operators\n\n1. **Update Shopware**\n   - Upgrade to the latest Shopware 6.6.x / 6.7.x release that includes this fix, **or**\n   - Install/update the latest Shopware Security Plugin version providing the hotfix for your Shopware 6 installation.\n2. **Update apps**\n   - Ensure all installed apps are updated to the latest versions provided by their manufacturers.\n   - If you suspect compromised keys or observe unexpected app behaviour, re\u2011install the affected app or trigger key rotation as documented by the app vendor.\n\n#### For App Manufacturers / Partners\n\n1. **Update SDKs / implementations**\n   - Update to the latest Shopware app SDKs (PHP / JS) or apply the documented changes if you maintain a custom implementation of the registration flow.\n   - Validate **both** `shopware-app-signature` and `shopware-shop-signature` for re\u2011registration requests.\n   - Always generate and store a new shop secret on re\u2011registration and only switch to it after a successful confirmation.\n2. **Review your apps**\n   - Verify that your app does not blindly accept changed `shop-url` values without validating signatures.\n   - Check any logic that exposes data or functionality based solely on HMAC signatures from shops and ensure it aligns with the hardened registration model.\n3. **Test your implementation**\n   - Use the updated tooling and guidance provided in your Shopware Account / partner channels to validate that your registration flow complies with the new requirements.",
  "id": "GHSA-c4p7-rwrg-pf6p",
  "modified": "2026-03-11T21:37:37Z",
  "published": "2026-03-11T19:24:06Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://github.com/shopware/shopware/security/advisories/GHSA-c4p7-rwrg-pf6p"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-31889"
    },
    {
      "type": "PACKAGE",
      "url": "https://github.com/shopware/shopware"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:L",
      "type": "CVSS_V3"
    }
  ],
  "summary": "Shopware vulnerable to a potential take over of app credentials"
}

Sightings

Author	Source	Type	Date

Nomenclature

Seen: The vulnerability was mentioned, discussed, or observed by the user.
Confirmed: The vulnerability has been validated from an analyst's perspective.
Published Proof of Concept: A public proof of concept is available for this vulnerability.
Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
Not confirmed: The user expressed doubt about the validity of the vulnerability.
Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.

Detection rules are retrieved from Rulezet.

Action not permitted

CVE-2026-31889 (GCVE-0-2026-31889)

FKIE_CVE-2026-31889

GHSA-C4P7-RWRG-PF6P

Summary

Affected Scope

Impact

Root Cause

Fix

Required Action

For Merchants / Shop Operators

For App Manufacturers / Partners

Tags

Sightings

Nomenclature