Skip to content
Fencer Intel
medium 5.3

CVE-2026-31888 json

Shopware has user enumeration via distinct error codes on Store API login endpoint

published 7mo ago modified last mo. also EUVD-2026-11298 , GHSA-gqc5-xv7m-gcjq

cvss
5.3
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.3%
EPSS 0.3% chance of exploitation in 30 days, percentile 16%
public exploits
0
none known

Summary

Shopware is an open commerce platform. Prior to 6.7.8.1 and 6.6.10.15, the Store API login endpoint (POST /store-api/account/login) returns different error codes depending on whether the submitted email address belongs to a registered customer (CHECKOUT__CUSTOMER_AUTH_BAD_CREDENTIALS) or is unknown (CHECKOUT__CUSTOMER_NOT_FOUND). The "not found" response also echoes the probed email address. This allows an unauthenticated attacker to enumerate valid customer accounts. The storefront login controller correctly unifies both error paths, but the Store API does not — indicating an inconsistent defense. This vulnerability is fixed in 6.7.8.1 and 6.6.10.15.

Patch / fix

  • packagist shopware/platform 6.6.10.14, 6.7.8.1
  • packagist shopware/core 6.6.10.15, 6.7.8.1
  • shopware shopware 6.6.10.14, 6.7.8.1

Is CVE-2026-31888 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
7mo ago

Exploit prediction

0.25% chance of exploitation in the next 30 days, higher than 16% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CNA 3.1 5.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
GitHub 3.1 5.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Affected packages

ecosystem package affected fixed in
packagist shopware/platform
>=6.7.0.0, <6.7.8.1
<6.6.10.14
6.7.8.1
6.6.10.14
packagist shopware/core
>=6.7.0.0, <6.7.8.1
<6.6.10.15
6.7.8.1
6.6.10.15

Affected products

  • shopware core
  • shopware platform

Classification

Weakness
  • CWE-204 Observable Response Discrepancy

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.