GHSA-M895-2HJ3-8CG9

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.

The application does not correctly enforce access controls, allowing a principal to access resources or operations beyond their granted permissions. Typical impact: unauthorized data access or execution of privileged operations.

GHSA-M895-2HJ3-8CG9 has a CVSS score of 5.3 (Medium). The vector is network-reachable, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (6.7.3.1, 6.6.10.7); upgrading removes the vulnerable code path.

Kodem intelligence

1. What is GHSA-M895-2HJ3-8CG9? GHSA-M895-2HJ3-8CG9 is a medium-severity incorrect authorization vulnerability in shopware/platform (composer), affecting versions >= 6.7.0.0, < 6.7.3.1. It is fixed in 6.7.3.1, 6.6.10.7. The application does not correctly enforce access controls, allowing a principal to access resources or operations beyond their granted permissions.
2. How severe is GHSA-M895-2HJ3-8CG9? GHSA-M895-2HJ3-8CG9 has a CVSS score of 5.3 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which packages are affected by GHSA-M895-2HJ3-8CG9?
   • shopware/platform (composer) (versions >= 6.7.0.0, < 6.7.3.1)
   • shopware/core (composer) (versions >= 6.7.0.0, < 6.7.3.1)
4. Is there a fix for GHSA-M895-2HJ3-8CG9? Yes. GHSA-M895-2HJ3-8CG9 is fixed in 6.7.3.1, 6.6.10.7. Upgrade to this version or later.
5. Is GHSA-M895-2HJ3-8CG9 exploitable, and should I be worried? Whether GHSA-M895-2HJ3-8CG9 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether GHSA-M895-2HJ3-8CG9 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix GHSA-M895-2HJ3-8CG9?
   • Upgrade shopware/platform to 6.7.3.1 or later
   • Upgrade shopware/platform to 6.6.10.7 or later
   • Upgrade shopware/core to 6.7.3.1 or later
   • Upgrade shopware/core to 6.6.10.7 or later