How severe is GHSA-hhcq-ph6w-494g?

GHSA-hhcq-ph6w-494g has a CVSS score of 5.3/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-hhcq-ph6w-494g?

GHSA-hhcq-ph6w-494g affects the following packages: shopware/core (Packagist), shopware/platform (Packagist), shopware/core (Packagist), shopware/platform (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-hhcq-ph6w-494g?

Update shopware/core to 6.5.8.13 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-hhcq-ph6w-494g is resolved across your whole dependency graph.

How do I detect GHSA-hhcq-ph6w-494g in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for shopware/core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-hhcq-ph6w-494g if there is no patch (or I can't update yet)?

Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Is GHSA-hhcq-ph6w-494g actively exploited in the wild?

No public exploit code has been indexed for GHSA-hhcq-ph6w-494g yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-hhcq-ph6w-494g?

GHSA-hhcq-ph6w-494g has an EPSS (Exploit Prediction Scoring System) score of 0.4%, placing it in the 37th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-hhcq-ph6w-494g?

GHSA-hhcq-ph6w-494g is classified as CWE-284 (CWE-284). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-hhcq-ph6w-494g published, and has it been updated?

GHSA-hhcq-ph6w-494g was published on August 8, 2024 and was last updated on August 12, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐘

🐘 Packagist

Not in CISA KEV

MEDIUM severity

Shopware vulnerable to Improper Access Control with ManyToMany associations in store-apiGHSA-hhcq-ph6w-494g

MEDIUMFix: shopware/core@a784aa1

GHSA-hhcq-ph6w-494g is a medium-severity (CVSS 5.3) CWE-284 vulnerability in shopware/core. A fix is available for shopware/core — see the affected versions and patch details below.

Also known asCVE-2024-42354

Published

Aug 8, 2024

Updated

Aug 12, 2024

Affected

4 pkgs

Patched

4 / 4

Exploits

None indexed

Exploitation data as of Nov 2, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-hhcq-ph6w-494g.

EPSS Exploitation Probability

via FIRST.org ↗

0.4%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs37th percentile — riskier than 37% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

4 pkgs affected

🐘shopware/core🐘shopware/platform🐘shopware/core🐘shopware/platform

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.

Description

Impact

The store-API works with regular entities and not expose all fields for the public API; fields need to be marked as ApiAware in the EntityDefinition. So only ApiAware fields of the EntityDefinition will be encoded to the final JSON.

The processing of the Criteria did not considered ManyToMany associations and so they were not considered properly and the protections didn't get used.

This issue cannot be reproduced with the default entities by Shopware, but can be triggered with extensions.

Patches

Update to Shopware 6.6.5.1 or 6.5.8.13.

Workarounds

For older versions of 6.2, 6.3, and 6.4, corresponding security measures are also available via a plugin. For the full range of functions, we recommend updating to the latest Shopware version.

Affected Packages

4 total 4 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`shopware/core`	all versions	6.5.8.13`composer require shopware/core:^6.5.8.13`
🐘Packagist	`shopware/platform`	all versions	6.5.8.13`composer require shopware/platform:^6.5.8.13`
🐘Packagist	`shopware/core`	≥ 6.6.0.0&&< 6.6.5.1	6.6.5.1`composer require shopware/core:^6.6.5.1`
🐘Packagist	`shopware/platform`	≥ 6.6.0.0&&< 6.6.5.1	6.6.5.1`composer require shopware/platform:^6.6.5.1`

Affected Products

1 product · 2 configurations

Application

shopwareshopware

≥ 6.6.0.0 && < 6.6.5.1

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for shopware/core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update shopware/core to 6.5.8.13 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-hhcq-ph6w-494g is resolved across your whole dependency graph.
Workarounds
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Frequently Asked Questions

### Impact The store-API works with regular entities and not expose all fields for the public API; fields need to be marked as ApiAware in the EntityDefinition. So only ApiAware fields of the EntityDefinition will be encoded to the final JSON. The processing of the Criteria did not considered ManyToMany associations and so they were not considered properly and the protections didn't get used. This issue cannot be reproduced with the default entities by Shopware, but can be triggered with extensions. ### Patches Update to Shopware 6.6.5.1 or 6.5.8.13. ### Workarounds For older versions of