Shopware vulnerable to MediaVisibilityRestrictionSubscriber bypass when reading media entities by aggregating fields individually
Published 21 Oct 2025 · Updated 10 Sept 2026
Affected packages
- Affected
- >=6.7.0.0 <6.7.3.1
- Fixed in
- 6.7.3.1
composer require shopware/platform:^6.7.3.1- Affected
- <6.6.10.7
- Fixed in
- 6.6.10.7
composer require shopware/platform:^6.6.10.7- Affected
- >=6.7.0.0 <6.7.3.1
- Fixed in
- 6.7.3.1
composer require shopware/core:^6.7.3.1- Affected
- <6.6.10.7
- Fixed in
- 6.6.10.7
composer require shopware/core:^6.6.10.7Details
In Shopware core and platform versions before 6.6.10.7 and 6.7.3.1, media visibility restrictions applied by MediaVisibilityRestrictionSubscriber are not enforced for aggregation API requests. Authorization filters are only injected during standard entity reads; aggregation queries can be constructed to bypass these checks and enumerate private media records such as invoices or other restricted documents. A low‑privilege backend user (e.g., product editor) can chain normal business flows (creating or viewing orders) with aggregation queries to disclose sensitive customer data including addresses and payment-related information contained within associated private media. The issue is resolved in 6.6.10.7 and 6.7.3.1.
Is GHSA-m895-2hj3-8cg9 in any of your client repos?
Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected shopware/platform, and gives you the command that fixes it.
References
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.