Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Medium, CVSS 5.3

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

CVE-2026-31888GHSA-gqc5-xv7m-gcjq

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (shopware/core 6.7.8.1, 6.6.10.15; shopware/platform 6.7.8.1, 6.6.10.14), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • Packagist shopware/core

    Affected
    >= 6.7.0.0, < 6.7.8.1< 6.6.10.15
    Fixed in
    6.6.10.15, 6.7.8.1

  • Packagist shopware/platform

    Affected
    >= 6.7.0.0, < 6.7.8.1< 6.6.10.14
    Fixed in
    6.6.10.14, 6.7.8.1

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
5.3 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
EPSS
  • CVE-2026-31888: 0.23% estimated exploitation activity in the next 30 days; percentile 14.09 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Summary 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 (CHECKOUTCUSTOMERAUTHBADCREDENTIALS) or is unknown (CHECKOUTCUSTOMERNOTFOUND). 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. CWE - CWE-204: Observable Response Discrepancy Description Distinct error codes leak account existence The login flow in AccountService::getCustomerByLogin() calls getCustomerByEmail() first, which throws CustomerNotFoundException if the email is not found. If the email IS found but the password is wrong, a separate BadCredentialsException is thrown: The two exception types produce clearly distinguishable API responses: Email not registered: Email registered,…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 1 · created ·

    Published from ghsa record GHSA-gqc5-xv7m-gcjq

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-31888

Advisory: Shopware has user enumeration via distinct error codes on Store API login endpoint
IDs: CVE-2026-31888, GHSA-gqc5-xv7m-gcjq
Record: https://patchnext.com/advisories/cve-2026-31888 (revision 1, source checked 26 Oct 2026, 14:38 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: shopware/core 6.7.8.1, 6.6.10.15; shopware/platform 6.7.8.1, 6.6.10.14. A vendor fix does not mean a deployment is fixed.

## Affected components
- Packagist shopware/core: affected >= 6.7.0.0, < 6.7.8.1; < 6.6.10.15; fixed in 6.6.10.15, 6.7.8.1
- Packagist shopware/platform: affected >= 6.7.0.0, < 6.7.8.1; < 6.6.10.14; fixed in 6.6.10.14, 6.7.8.1

## Suggested inspection (read-only)
- Packagist shopware/core: check the installed version with your package manager.
- Packagist shopware/platform: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on shopware/core, shopware/platform.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-gqc5-xv7m-gcjq (GitHub-reviewed advisory GHSA-gqc5-xv7m-gcjq lists affected ranges: Packagist shopware/platform >=6.7.0.0 =0 =6.7.0.0 =0 <6.6.10.15)

Commands are suggestions: review each one before running it.

Loading voting…