How severe is GHSA-c4p7-rwrg-pf6p?

GHSA-c4p7-rwrg-pf6p has a CVSS score of 8.9/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-c4p7-rwrg-pf6p?

GHSA-c4p7-rwrg-pf6p affects the following packages: shopware/platform (Packagist), shopware/platform (Packagist), shopware/core (Packagist), shopware/core (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-c4p7-rwrg-pf6p?

Update shopware/platform to 6.7.8.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-c4p7-rwrg-pf6p is resolved across your whole dependency graph.

How do I detect GHSA-c4p7-rwrg-pf6p in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for shopware/platform. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-c4p7-rwrg-pf6p if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-c4p7-rwrg-pf6p?

O3 pinpoints whether GHSA-c4p7-rwrg-pf6p is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-c4p7-rwrg-pf6p actively exploited in the wild?

No public exploit code has been indexed for GHSA-c4p7-rwrg-pf6p 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-c4p7-rwrg-pf6p?

GHSA-c4p7-rwrg-pf6p has an EPSS (Exploit Prediction Scoring System) score of 0.3%, placing it in the 18th 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-c4p7-rwrg-pf6p?

GHSA-c4p7-rwrg-pf6p is classified as CWE-290 (CWE-290). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-c4p7-rwrg-pf6p published, and has it been updated?

GHSA-c4p7-rwrg-pf6p was published on March 11, 2026 and was last updated on March 13, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐘 Packagist

GHSA-c4p7-rwrg-pf6p

HIGH

Shopware vulnerable to a potential take over of app credentials

Also known asCVE-2026-31889

Published

Mar 11, 2026

Updated

Mar 13, 2026

Affected

4 pkgs

Patched

4 / 4

Exploits

None indexed

EPSS Exploitation Probability

via FIRST.org ↗

0.3%probability of exploitation in next 30 days

Lower Risk18th percentile+0.17%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

4 pkgs affected

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

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

Summary

We identified and fixed a vulnerability in the Shopware app registration flow that could, under specific conditions, allow attackers to take over the communication channel between a shop and an app. By abusing app re‑registration, an attacker could redirect app traffic to an attacker‑controlled domain and potentially obtain API credentials intended for the legitimate shop. We have no evidence that this vulnerability has been exploited.

Affected Scope

All apps (public and private) that use a registrationUrl in their app manifest and rely on the legacy HMAC‑based registration flow.
Both on‑premise and cloud installations are affected until updated to a fixed Shopware version or protected by the latest Shopware Security Plugin.
Shopware services and first‑party apps using the affected SDKs were reviewed and patched. The vulnerability does not affect core storefront or administration authentication; it is limited to the app system’s registration and re‑registration mechanism.

Impact

In a successful attack, an attacker who already knows certain app‑side secrets could:

Re‑register an existing app installation with a domain under their control.
Intercept App → Shop communication and cause data tampering (“data poisoning”).
Obtain API integration credentials of the shop with the permissions granted to the app. Shop owners and app manufacturers would typically observe this as “app malfunction” rather than an obvious security issue, which increases the need for hardening.

Root Cause

The legacy app registration flow used HMAC‑based authentication without sufficiently binding a shop installation to its original domain. During re‑registration, the shop-url could be updated without proving control over the previously registered shop or domain. This made targeted hijacking of app communication feasible if an attacker possessed the relevant app‑side secret.

Fix

We have hardened the app registration and re‑registration process:

Dual signature requirement: Re‑registration now requires both the app secret and the existing shop secret to be presented and validated.
Mandatory secret rotation: On successful re‑registration, a new shop secret is generated and verified; the previous secret is invalidated after a short grace period.
Stricter validation: Shopware only accepts updated shop URLs and secrets once the full confirmation flow has completed successfully.
Improved logging and monitoring: All re‑registrations are now logged with additional metadata to help detect abuse patterns. These changes are delivered via:
Updated Shopware core releases (6.6.x, 6.7.x), and
Updated versions of the Shopware Security Plugin for supported older versions,
Updated official SDKs (e.g. PHP and JavaScript app SDKs).

Required Action

For Merchants / Shop Operators

Update Shopware
- Upgrade to the latest Shopware 6.6.x / 6.7.x release that includes this fix, or
- Install/update the latest Shopware Security Plugin version providing the hotfix for your Shopware 6 installation.
Update apps
- Ensure all installed apps are updated to the latest versions provided by their manufacturers.
- If you suspect compromised keys or observe unexpected app behaviour, re‑install the affected app or trigger key rotation as documented by the app vendor.

For App Manufacturers / Partners

Update SDKs / implementations
- Update to the latest Shopware app SDKs (PHP / JS) or apply the documented changes if you maintain a custom implementation of the registration flow.
- Validate both shopware-app-signature and shopware-shop-signature for re‑registration requests.
- Always generate and store a new shop secret on re‑registration and only switch to it after a successful confirmation.
Review your apps
- Verify that your app does not blindly accept changed shop-url values without validating signatures.
- Check any logic that exposes data or functionality based solely on HMAC signatures from shops and ensure it aligns with the hardened registration model.
Test your implementation
- Use the updated tooling and guidance provided in your Shopware Account / partner channels to validate that your registration flow complies with the new requirements.

Affected Packages

4 total 4 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`shopware/platform`	≥ 6.7.0.0&&< 6.7.8.1	6.7.8.1
🐘Packagist	`shopware/platform`	all versions	6.6.10.15
🐘Packagist	`shopware/core`	≥ 6.7.0.0&&< 6.7.8.1	6.7.8.1
🐘Packagist	`shopware/core`	all versions	6.6.10.15

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for shopware/platform. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update shopware/platform to 6.7.8.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-c4p7-rwrg-pf6p is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-c4p7-rwrg-pf6p is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-c4p7-rwrg-pf6p. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Summary We identified and fixed a vulnerability in the Shopware app registration flow that could, under specific conditions, allow attackers to take over the communication channel between a shop and an app. By abusing app re‑registration, an attacker could redirect app traffic to an attacker‑controlled domain and potentially obtain API credentials intended for the legitimate shop. We have no evidence that this vulnerability has been exploited. --- ### Affected Scope - All apps (public and private) that use a `registrationUrl` in their app manifest and rely on the legacy HMAC‑based regi

O3 Security · Impact-Aware SCA

Is GHSA-c4p7-rwrg-pf6p in your dependencies?

O3 detects GHSA-c4p7-rwrg-pf6p across Packagist dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works