# 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 MediaVisibilityRestrictionSubsc

> Low-privilege users can bypass media visibility restrictions via aggregation queries to disclose sensitive customer data in Shopware.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 21 Oct 2025

## What is GHSA-m895-2hj3-8cg9?

GHSA-m895-2hj3-8cg9 is a missing authorization vulnerability in shopware/core, published on 21 Oct 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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.

## Which versions are affected by GHSA-m895-2hj3-8cg9?

8 open source packages ship an affected version, including shopware/core and shopware/platform.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `shopware/core` | Packagist | All versions | 6.6.10.7 |
| `shopware/core` | Packagist | All versions | 6.6.10.7 |
| `shopware/core` | Packagist | From 6.7.0.0 | 6.7.3.1 |
| `shopware/core` | Packagist | From 6.7.0.0 | 6.7.3.1 |
| `shopware/platform` | Packagist | All versions | 6.6.10.7 |
| `shopware/platform` | Packagist | All versions | 6.6.10.7 |
| `shopware/platform` | Packagist | From 6.7.0.0 | 6.7.3.1 |
| `shopware/platform` | Packagist | From 6.7.0.0 | 6.7.3.1 |

## How do I fix GHSA-m895-2hj3-8cg9?

Upgrade shopware/core to a fixed version for your release line: 6.6.10.7 or 6.7.3.1.

## Is GHSA-m895-2hj3-8cg9 being exploited?

There is no known exploitation of GHSA-m895-2hj3-8cg9 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-m895-2hj3-8cg9 and fix it if it is affected.

What it is: GHSA-m895-2hj3-8cg9 is a missing authorization vulnerability in shopware/core, published on 21 Oct 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of GHSA-m895-2hj3-8cg9 in the wild and no public exploit code.

Affected packages and fixed versions:
- shopware/core (Packagist): affected all versions; fixed in 6.6.10.7
- shopware/core (Packagist): affected all versions; fixed in 6.6.10.7
- shopware/core (Packagist): affected from 6.7.0.0; fixed in 6.7.3.1
- shopware/core (Packagist): affected from 6.7.0.0; fixed in 6.7.3.1
- shopware/platform (Packagist): affected all versions; fixed in 6.6.10.7
- shopware/platform (Packagist): affected all versions; fixed in 6.6.10.7
- shopware/platform (Packagist): affected from 6.7.0.0; fixed in 6.7.3.1
- shopware/platform (Packagist): affected from 6.7.0.0; fixed in 6.7.3.1

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/GHSA-m895-2hj3-8cg9/ (Markdown: https://insights.sbomify.com/GHSA-m895-2hj3-8cg9/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-m895-2hj3-8cg9

---
From sbomify Insights: https://insights.sbomify.com/GHSA-m895-2hj3-8cg9/
Summaries are generated and may contain mistakes; the official description above is the record.