Approved changes feed: RSS · Atom
cpe:2.3:a:shopware:core:*:*:*:*:*:*:*:*
part: a version: * update: *
| Vendor | Shopware (03d0634f-d86e-5a60-ad92-ec84f39a59ef) |
|---|---|
| Product | Core (6821aaf2-7dec-5a45-a6ce-e13beb2b1438) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from gcve-enriched-dumps CVE data |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2026-31889 |
vulnerable | 2026-06-08 07:57:16.050657 |
Shopware has a potential take over of app credentials
HIGH (8.9)
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.
Published: 2026-03-11T18:56:23.171Z
Updated: 2026-03-12T20:04:11.623Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-31888 |
vulnerable | 2026-06-08 07:57:16.050192 |
Shopware has user enumeration via distinct error codes on Store API login endpoint
MEDIUM (5.3)
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.
Published: 2026-03-11T18:53:03.018Z
Updated: 2026-03-12T20:02:47.581Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-31887 |
vulnerable | 2026-06-08 07:57:16.048165 |
Shopware unauthenticated data extraction possible through store-api.order endpoint
Shopware is an open commerce platform. Prior to 6.7.8.1 and 6.6.10.15, an insufficient check on the filter types for unauthenticated customers allows access to orders of other customers. This is part of the deepLinkCode support on the store-api.order endpoint. This vulnerability is fixed in 6.7.8.1 and 6.6.10.15.
Published: 2026-03-11T18:49:46.294Z
Updated: 2026-03-12T20:02:14.866Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.