{"items":[{"id":"NVI-00008314","kind":"vulnerability","title":"Shopware has user enumeration via distinct error codes on Store API login endpoint","revision":4,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected.","NVD lastModified does not establish freshness of every associated CPE record."],"lifecycle":"active","identifiers":["GHSA-gqc5-xv7m-gcjq","CVE-2026-31888"],"plain_summary":"OSV carries this publisher advisory for shopware/platform, shopware/platform, shopware/core, shopware/core. This is an aggregated source copy; consult the original publisher and compare update dates.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"The original advisory lists fixed boundaries 6.7.8.1 for shopware/platform. Confirm the publisher’s latest guidance.","source_ids":["sr-fe7eca14eb3669966c21a18bb14c50a1"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 6.6.10.14 for shopware/platform. Confirm the publisher’s latest guidance.","source_ids":["sr-fe7eca14eb3669966c21a18bb14c50a1"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 6.7.8.1 for shopware/core. Confirm the publisher’s latest guidance.","source_ids":["sr-fe7eca14eb3669966c21a18bb14c50a1"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 6.6.10.15 for shopware/core. Confirm the publisher’s latest guidance.","source_ids":["sr-fe7eca14eb3669966c21a18bb14c50a1"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-14b47998d650e1eaed1f7c9cb94f99df"],"action_type":"investigate","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[{"kind":"CVSS","as_of":"2026-06-17T10:34:42.087Z","value":"5.3 MEDIUM (3.1)","meaning":"security-advisories@github.com severity; no combined Null risk score.","source_id":"sr-0ee96405703b3e34f3eb22a7a4a3391b"},{"kind":"EPSS","as_of":"2026-11-03T12:00:27.000Z","value":"0.231%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.14095. Missing scores are unknown.","source_id":"sr-14b47998d650e1eaed1f7c9cb94f99df"}],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-fe7eca14eb3669966c21a18bb14c50a1","url":"https://github.com/advisories/GHSA-gqc5-xv7m-gcjq","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-gqc5-xv7m-gcjq","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:42:20.421Z"},{"id":"sr-0ee96405703b3e34f3eb22a7a4a3391b","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31888","basis":"official_catalog","notes":"This product uses data from the NVD API but is not endorsed or certified by the NVD.","title":"CVE-2026-31888","publisher":"NIST National Vulnerability Database","observed_at":"2026-11-03T17:45:11.098Z"},{"id":"sr-14b47998d650e1eaed1f7c9cb94f99df","url":"https://www.first.org/epss/data.html","basis":"official_catalog","notes":"FIRST EPSS; probability of exploitation in the next 30 days, not local compromise. Dataset date/model retained; FIRST services terms apply.","title":"CVE-2026-31888","publisher":"FIRST EPSS","observed_at":"2026-11-03T17:44:07.782Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-fe7eca14eb3669966c21a18bb14c50a1"],"technology":"shopware/platform","known_exclusions":[],"conditions_summary":"## Summary\n\nThe 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.\n\n## CWE\n\n- **CWE-204**: Observable Response Discrepancy\n\n## Description\n\n### Distinct error codes leak account existence\n\nThe 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:\n\n```php\n// src/Core/Checkout/Customer/SalesChannel/AccountService.php:116-145\npublic function getCustomerByLogin(string $email, string $password, SalesChannelContext $context): CustomerEntity\n{\n    if ($this->isPasswordTooLong($password)) {\n        throw CustomerExce","public_affected_ranges":["ECOSYSTEM: introduced 6.7.0.0; fixed 6.7.8.1"]},{"certainty":"source_listed","source_ids":["sr-fe7eca14eb3669966c21a18bb14c50a1"],"technology":"shopware/platform","known_exclusions":[],"conditions_summary":"## Summary\n\nThe 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.\n\n## CWE\n\n- **CWE-204**: Observable Response Discrepancy\n\n## Description\n\n### Distinct error codes leak account existence\n\nThe 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:\n\n```php\n// src/Core/Checkout/Customer/SalesChannel/AccountService.php:116-145\npublic function getCustomerByLogin(string $email, string $password, SalesChannelContext $context): CustomerEntity\n{\n    if ($this->isPasswordTooLong($password)) {\n        throw CustomerExce","public_affected_ranges":["ECOSYSTEM: introduced 0; fixed 6.6.10.14"]},{"certainty":"source_listed","source_ids":["sr-fe7eca14eb3669966c21a18bb14c50a1"],"technology":"shopware/core","known_exclusions":[],"conditions_summary":"## Summary\n\nThe 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.\n\n## CWE\n\n- **CWE-204**: Observable Response Discrepancy\n\n## Description\n\n### Distinct error codes leak account existence\n\nThe 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:\n\n```php\n// src/Core/Checkout/Customer/SalesChannel/AccountService.php:116-145\npublic function getCustomerByLogin(string $email, string $password, SalesChannelContext $context): CustomerEntity\n{\n    if ($this->isPasswordTooLong($password)) {\n        throw CustomerExce","public_affected_ranges":["ECOSYSTEM: introduced 6.7.0.0; fixed 6.7.8.1"]},{"certainty":"source_listed","source_ids":["sr-fe7eca14eb3669966c21a18bb14c50a1"],"technology":"shopware/core","known_exclusions":[],"conditions_summary":"## Summary\n\nThe 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.\n\n## CWE\n\n- **CWE-204**: Observable Response Discrepancy\n\n## Description\n\n### Distinct error codes leak account existence\n\nThe 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:\n\n```php\n// src/Core/Checkout/Customer/SalesChannel/AccountService.php:116-145\npublic function getCustomerByLogin(string $email, string $password, SalesChannelContext $context): CustomerEntity\n{\n    if ($this->isPasswordTooLong($password)) {\n        throw CustomerExce","public_affected_ranges":["ECOSYSTEM: introduced 0; fixed 6.6.10.15"]}],"null_published_at":"2026-11-06T00:29:57.322Z","source_updated_at":"2026-09-10T03:50:39.383Z","source_disclosed_at":"2026-03-11T19:23:49.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"Dated EPSS estimate updated; this is not a new disclosure or proof of exploitation.","null_first_observed_at":"2026-10-31T21:42:20.421Z"},{"id":"NVI-00008314","kind":"vulnerability","title":"Shopware has user enumeration via distinct error codes on Store API login endpoint","revision":3,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected.","NVD lastModified does not establish freshness of every associated CPE record."],"lifecycle":"active","identifiers":["GHSA-gqc5-xv7m-gcjq","CVE-2026-31888"],"plain_summary":"OSV carries this publisher advisory for shopware/platform, shopware/platform, shopware/core, shopware/core. This is an aggregated source copy; consult the original publisher and compare update dates.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"The original advisory lists fixed boundaries 6.7.8.1 for shopware/platform. Confirm the publisher’s latest guidance.","source_ids":["sr-fe7eca14eb3669966c21a18bb14c50a1"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 6.6.10.14 for shopware/platform. Confirm the publisher’s latest guidance.","source_ids":["sr-fe7eca14eb3669966c21a18bb14c50a1"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 6.7.8.1 for shopware/core. Confirm the publisher’s latest guidance.","source_ids":["sr-fe7eca14eb3669966c21a18bb14c50a1"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 6.6.10.15 for shopware/core. Confirm the publisher’s latest guidance.","source_ids":["sr-fe7eca14eb3669966c21a18bb14c50a1"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-76b947819dfd0ee09b5f1e7b65abca27"],"action_type":"investigate","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[{"kind":"CVSS","as_of":"2026-06-17T10:34:42.087Z","value":"5.3 MEDIUM (3.1)","meaning":"security-advisories@github.com severity; no combined Null risk score.","source_id":"sr-0ee96405703b3e34f3eb22a7a4a3391b"},{"kind":"EPSS","as_of":"2026-10-31T12:00:27.000Z","value":"0.231%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.14069. Missing scores are unknown.","source_id":"sr-76b947819dfd0ee09b5f1e7b65abca27"}],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-fe7eca14eb3669966c21a18bb14c50a1","url":"https://github.com/advisories/GHSA-gqc5-xv7m-gcjq","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-gqc5-xv7m-gcjq","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:42:20.421Z"},{"id":"sr-0ee96405703b3e34f3eb22a7a4a3391b","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31888","basis":"official_catalog","notes":"This product uses data from the NVD API but is not endorsed or certified by the NVD.","title":"CVE-2026-31888","publisher":"NIST National Vulnerability Database","observed_at":"2026-11-03T17:45:11.098Z"},{"id":"sr-76b947819dfd0ee09b5f1e7b65abca27","url":"https://www.first.org/epss/data.html","basis":"official_catalog","notes":"FIRST EPSS; probability of exploitation in the next 30 days, not local compromise. Dataset date/model retained; FIRST services terms apply.","title":"CVE-2026-31888","publisher":"FIRST EPSS","observed_at":"2026-10-31T22:06:15.376Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-fe7eca14eb3669966c21a18bb14c50a1"],"technology":"shopware/platform","known_exclusions":[],"conditions_summary":"## Summary\n\nThe 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.\n\n## CWE\n\n- **CWE-204**: Observable Response Discrepancy\n\n## Description\n\n### Distinct error codes leak account existence\n\nThe 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:\n\n```php\n// src/Core/Checkout/Customer/SalesChannel/AccountService.php:116-145\npublic function getCustomerByLogin(string $email, string $password, SalesChannelContext $context): CustomerEntity\n{\n    if ($this->isPasswordTooLong($password)) {\n        throw CustomerExce","public_affected_ranges":["ECOSYSTEM: introduced 6.7.0.0; fixed 6.7.8.1"]},{"certainty":"source_listed","source_ids":["sr-fe7eca14eb3669966c21a18bb14c50a1"],"technology":"shopware/platform","known_exclusions":[],"conditions_summary":"## Summary\n\nThe 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.\n\n## CWE\n\n- **CWE-204**: Observable Response Discrepancy\n\n## Description\n\n### Distinct error codes leak account existence\n\nThe 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:\n\n```php\n// src/Core/Checkout/Customer/SalesChannel/AccountService.php:116-145\npublic function getCustomerByLogin(string $email, string $password, SalesChannelContext $context): CustomerEntity\n{\n    if ($this->isPasswordTooLong($password)) {\n        throw CustomerExce","public_affected_ranges":["ECOSYSTEM: introduced 0; fixed 6.6.10.14"]},{"certainty":"source_listed","source_ids":["sr-fe7eca14eb3669966c21a18bb14c50a1"],"technology":"shopware/core","known_exclusions":[],"conditions_summary":"## Summary\n\nThe 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.\n\n## CWE\n\n- **CWE-204**: Observable Response Discrepancy\n\n## Description\n\n### Distinct error codes leak account existence\n\nThe 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:\n\n```php\n// src/Core/Checkout/Customer/SalesChannel/AccountService.php:116-145\npublic function getCustomerByLogin(string $email, string $password, SalesChannelContext $context): CustomerEntity\n{\n    if ($this->isPasswordTooLong($password)) {\n        throw CustomerExce","public_affected_ranges":["ECOSYSTEM: introduced 6.7.0.0; fixed 6.7.8.1"]},{"certainty":"source_listed","source_ids":["sr-fe7eca14eb3669966c21a18bb14c50a1"],"technology":"shopware/core","known_exclusions":[],"conditions_summary":"## Summary\n\nThe 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.\n\n## CWE\n\n- **CWE-204**: Observable Response Discrepancy\n\n## Description\n\n### Distinct error codes leak account existence\n\nThe 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:\n\n```php\n// src/Core/Checkout/Customer/SalesChannel/AccountService.php:116-145\npublic function getCustomerByLogin(string $email, string $password, SalesChannelContext $context): CustomerEntity\n{\n    if ($this->isPasswordTooLong($password)) {\n        throw CustomerExce","public_affected_ranges":["ECOSYSTEM: introduced 0; fixed 6.6.10.15"]}],"null_published_at":"2026-11-04T10:04:35.904Z","source_updated_at":"2026-09-10T03:50:39.383Z","source_disclosed_at":"2026-03-11T19:23:49.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"Source facts changed; compare the preserved prior revision.","null_first_observed_at":"2026-10-31T21:42:20.421Z"},{"id":"NVI-00008314","kind":"vulnerability","title":"Shopware has user enumeration via distinct error codes on Store API login endpoint","revision":2,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-gqc5-xv7m-gcjq","CVE-2026-31888"],"plain_summary":"OSV carries this publisher advisory for shopware/platform, shopware/platform, shopware/core, shopware/core. This is an aggregated source copy; consult the original publisher and compare update dates.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"The original advisory lists fixed boundaries 6.7.8.1 for shopware/platform. Confirm the publisher’s latest guidance.","source_ids":["sr-fe7eca14eb3669966c21a18bb14c50a1"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 6.6.10.14 for shopware/platform. Confirm the publisher’s latest guidance.","source_ids":["sr-fe7eca14eb3669966c21a18bb14c50a1"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 6.7.8.1 for shopware/core. Confirm the publisher’s latest guidance.","source_ids":["sr-fe7eca14eb3669966c21a18bb14c50a1"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 6.6.10.15 for shopware/core. Confirm the publisher’s latest guidance.","source_ids":["sr-fe7eca14eb3669966c21a18bb14c50a1"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-76b947819dfd0ee09b5f1e7b65abca27"],"action_type":"investigate","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[{"kind":"EPSS","as_of":"2026-10-31T12:00:27.000Z","value":"0.231%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.14069. Missing scores are unknown.","source_id":"sr-76b947819dfd0ee09b5f1e7b65abca27"}],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-fe7eca14eb3669966c21a18bb14c50a1","url":"https://github.com/advisories/GHSA-gqc5-xv7m-gcjq","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-gqc5-xv7m-gcjq","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:42:20.421Z"},{"id":"sr-76b947819dfd0ee09b5f1e7b65abca27","url":"https://www.first.org/epss/data.html","basis":"official_catalog","notes":"FIRST EPSS; probability of exploitation in the next 30 days, not local compromise. Dataset date/model retained; FIRST services terms apply.","title":"CVE-2026-31888","publisher":"FIRST EPSS","observed_at":"2026-10-31T22:06:15.376Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-fe7eca14eb3669966c21a18bb14c50a1"],"technology":"shopware/platform","known_exclusions":[],"conditions_summary":"## Summary\n\nThe 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.\n\n## CWE\n\n- **CWE-204**: Observable Response Discrepancy\n\n## Description\n\n### Distinct error codes leak account existence\n\nThe 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:\n\n```php\n// src/Core/Checkout/Customer/SalesChannel/AccountService.php:116-145\npublic function getCustomerByLogin(string $email, string $password, SalesChannelContext $context): CustomerEntity\n{\n    if ($this->isPasswordTooLong($password)) {\n        throw CustomerExce","public_affected_ranges":["ECOSYSTEM: introduced 6.7.0.0; fixed 6.7.8.1"]},{"certainty":"source_listed","source_ids":["sr-fe7eca14eb3669966c21a18bb14c50a1"],"technology":"shopware/platform","known_exclusions":[],"conditions_summary":"## Summary\n\nThe 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.\n\n## CWE\n\n- **CWE-204**: Observable Response Discrepancy\n\n## Description\n\n### Distinct error codes leak account existence\n\nThe 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:\n\n```php\n// src/Core/Checkout/Customer/SalesChannel/AccountService.php:116-145\npublic function getCustomerByLogin(string $email, string $password, SalesChannelContext $context): CustomerEntity\n{\n    if ($this->isPasswordTooLong($password)) {\n        throw CustomerExce","public_affected_ranges":["ECOSYSTEM: introduced 0; fixed 6.6.10.14"]},{"certainty":"source_listed","source_ids":["sr-fe7eca14eb3669966c21a18bb14c50a1"],"technology":"shopware/core","known_exclusions":[],"conditions_summary":"## Summary\n\nThe 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.\n\n## CWE\n\n- **CWE-204**: Observable Response Discrepancy\n\n## Description\n\n### Distinct error codes leak account existence\n\nThe 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:\n\n```php\n// src/Core/Checkout/Customer/SalesChannel/AccountService.php:116-145\npublic function getCustomerByLogin(string $email, string $password, SalesChannelContext $context): CustomerEntity\n{\n    if ($this->isPasswordTooLong($password)) {\n        throw CustomerExce","public_affected_ranges":["ECOSYSTEM: introduced 6.7.0.0; fixed 6.7.8.1"]},{"certainty":"source_listed","source_ids":["sr-fe7eca14eb3669966c21a18bb14c50a1"],"technology":"shopware/core","known_exclusions":[],"conditions_summary":"## Summary\n\nThe 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.\n\n## CWE\n\n- **CWE-204**: Observable Response Discrepancy\n\n## Description\n\n### Distinct error codes leak account existence\n\nThe 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:\n\n```php\n// src/Core/Checkout/Customer/SalesChannel/AccountService.php:116-145\npublic function getCustomerByLogin(string $email, string $password, SalesChannelContext $context): CustomerEntity\n{\n    if ($this->isPasswordTooLong($password)) {\n        throw CustomerExce","public_affected_ranges":["ECOSYSTEM: introduced 0; fixed 6.6.10.15"]}],"null_published_at":"2026-11-01T19:14:01.602Z","source_updated_at":"2026-09-10T03:50:39.383Z","source_disclosed_at":"2026-03-11T19:23:49.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"Dated EPSS estimate updated; this is not a new disclosure or proof of exploitation.","null_first_observed_at":"2026-10-31T21:42:20.421Z"},{"id":"NVI-00008314","kind":"vulnerability","title":"Shopware has user enumeration via distinct error codes on Store API login endpoint","revision":1,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-gqc5-xv7m-gcjq","CVE-2026-31888"],"plain_summary":"OSV carries this publisher advisory for shopware/platform, shopware/platform, shopware/core, shopware/core. This is an aggregated source copy; consult the original publisher and compare update dates.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"The original advisory lists fixed boundaries 6.7.8.1 for shopware/platform. Confirm the publisher’s latest guidance.","source_ids":["sr-fe7eca14eb3669966c21a18bb14c50a1"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 6.6.10.14 for shopware/platform. Confirm the publisher’s latest guidance.","source_ids":["sr-fe7eca14eb3669966c21a18bb14c50a1"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 6.7.8.1 for shopware/core. Confirm the publisher’s latest guidance.","source_ids":["sr-fe7eca14eb3669966c21a18bb14c50a1"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 6.6.10.15 for shopware/core. Confirm the publisher’s latest guidance.","source_ids":["sr-fe7eca14eb3669966c21a18bb14c50a1"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-fe7eca14eb3669966c21a18bb14c50a1","url":"https://github.com/advisories/GHSA-gqc5-xv7m-gcjq","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-gqc5-xv7m-gcjq","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:42:20.421Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-fe7eca14eb3669966c21a18bb14c50a1"],"technology":"shopware/platform","known_exclusions":[],"conditions_summary":"## Summary\n\nThe 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.\n\n## CWE\n\n- **CWE-204**: Observable Response Discrepancy\n\n## Description\n\n### Distinct error codes leak account existence\n\nThe 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:\n\n```php\n// src/Core/Checkout/Customer/SalesChannel/AccountService.php:116-145\npublic function getCustomerByLogin(string $email, string $password, SalesChannelContext $context): CustomerEntity\n{\n    if ($this->isPasswordTooLong($password)) {\n        throw CustomerExce","public_affected_ranges":["ECOSYSTEM: introduced 6.7.0.0; fixed 6.7.8.1"]},{"certainty":"source_listed","source_ids":["sr-fe7eca14eb3669966c21a18bb14c50a1"],"technology":"shopware/platform","known_exclusions":[],"conditions_summary":"## Summary\n\nThe 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.\n\n## CWE\n\n- **CWE-204**: Observable Response Discrepancy\n\n## Description\n\n### Distinct error codes leak account existence\n\nThe 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:\n\n```php\n// src/Core/Checkout/Customer/SalesChannel/AccountService.php:116-145\npublic function getCustomerByLogin(string $email, string $password, SalesChannelContext $context): CustomerEntity\n{\n    if ($this->isPasswordTooLong($password)) {\n        throw CustomerExce","public_affected_ranges":["ECOSYSTEM: introduced 0; fixed 6.6.10.14"]},{"certainty":"source_listed","source_ids":["sr-fe7eca14eb3669966c21a18bb14c50a1"],"technology":"shopware/core","known_exclusions":[],"conditions_summary":"## Summary\n\nThe 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.\n\n## CWE\n\n- **CWE-204**: Observable Response Discrepancy\n\n## Description\n\n### Distinct error codes leak account existence\n\nThe 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:\n\n```php\n// src/Core/Checkout/Customer/SalesChannel/AccountService.php:116-145\npublic function getCustomerByLogin(string $email, string $password, SalesChannelContext $context): CustomerEntity\n{\n    if ($this->isPasswordTooLong($password)) {\n        throw CustomerExce","public_affected_ranges":["ECOSYSTEM: introduced 6.7.0.0; fixed 6.7.8.1"]},{"certainty":"source_listed","source_ids":["sr-fe7eca14eb3669966c21a18bb14c50a1"],"technology":"shopware/core","known_exclusions":[],"conditions_summary":"## Summary\n\nThe 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.\n\n## CWE\n\n- **CWE-204**: Observable Response Discrepancy\n\n## Description\n\n### Distinct error codes leak account existence\n\nThe 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:\n\n```php\n// src/Core/Checkout/Customer/SalesChannel/AccountService.php:116-145\npublic function getCustomerByLogin(string $email, string $password, SalesChannelContext $context): CustomerEntity\n{\n    if ($this->isPasswordTooLong($password)) {\n        throw CustomerExce","public_affected_ranges":["ECOSYSTEM: introduced 0; fixed 6.6.10.15"]}],"null_published_at":"2026-10-31T22:13:22.839Z","source_updated_at":"2026-09-10T03:50:39.383Z","source_disclosed_at":"2026-03-11T19:23:49.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"First indexed by Null; source disclosure date is shown separately.","null_first_observed_at":"2026-10-31T21:42:20.421Z"}],"next_cursor":null,"snapshot_revision":"42594"}