Advisory record · GHSA-hh7j-6x3q-f52h

Shopware 6 allows attackers to check for registered accounts through the store-api

CVSS 5.5 MediumEPSS 0.0041 · 35th percentile

Published by the GitHub Advisory Database at 8 Apr 2025, 14:50 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
shopware/corePackagist>=6.6.0.0, <6.6.10.3 || >=6.7.0.0-rc1, <6.7.0.0-rc2 || <6.5.8.186.6.10.3, 6.7.0.0-rc2, 6.5.8.18
shopware/platformPackagist>=6.6.0.0, <6.6.10.3 || >=6.7.0.0-rc1, <6.7.0.0-rc2 || <6.5.8.186.6.10.3, 6.7.0.0-rc2, 6.5.8.18
Identifiers
GHSA-hh7j-6x3q-f52h · CVE-2025-30150 · PKSA-4xth-xj4w-m8t1 · PKSA-dbxn-psgm-2qmr
Weakness (CWE)
CWE-204
Published
8 Apr 2025
Updated
10 Sept 2025

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Shopware 6 (packages shopware/core and shopware/platform) in versions before 6.5.8.18, from 6.6.0.0 before 6.6.10.3, and from 6.7.0.0-rc1 before 6.7.0.0-rc2 is affected. An unauthenticated attacker using the store-api password recovery endpoint can tell whether a given e-mail address has an account, because the responses differ for registered and unregistered addresses. Upgrade to 6.5.8.18, 6.6.10.3, or 6.7.0.0-rc2, depending on your release line. The source says that for older 6.4 and 6.5 versions, a plugin provides some protection.

Written 3 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
5.5 Medium 4.0 CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:P/U:Green CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0041, the 35th percentile, on 7 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:26 UTC First seen by agentprime
  2. 31 Oct 2026, 14:26 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.