How severe is GHSA-r2vg-hvjm-fg38?

GHSA-r2vg-hvjm-fg38 has a CVSS score of 4.3/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-r2vg-hvjm-fg38?

GHSA-r2vg-hvjm-fg38 affects the following packages: shopware/platform (Packagist), shopware/platform (Packagist), shopware/core (Packagist), shopware/core (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-r2vg-hvjm-fg38?

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

How do I detect GHSA-r2vg-hvjm-fg38 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-r2vg-hvjm-fg38 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-r2vg-hvjm-fg38?

O3 pinpoints whether GHSA-r2vg-hvjm-fg38 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-r2vg-hvjm-fg38 actively exploited in the wild?

No public exploit code has been indexed for GHSA-r2vg-hvjm-fg38 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.

When was GHSA-r2vg-hvjm-fg38 published, and has it been updated?

GHSA-r2vg-hvjm-fg38 was published on October 21, 2025 and was last updated on October 22, 2025. 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-r2vg-hvjm-fg38

MEDIUM

Shopware Customer Orders can be canceled, even if refunds are disabled

Published

Oct 21, 2025

Updated

Oct 22, 2025

Affected

4 pkgs

Patched

4 / 4

Exploits

None indexed

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

Refunds in general can be enabled through the administration setting core.cart.enableOrderRefunds (in the cart panel).Which visually shows and hides the button. However, using a custom crafted request, a customer can still cancel his own orders.As this is not checked inside the route (and also not in the controller): https://github.com/shopware/shopware/blob/trunk/src/Storefront/Controller/AccountOrderController.php#L98 https://github.com/shopware/shopware/blob/trunk/src/Core/Checkout/Order/SalesChannel/CancelOrderRoute.php

To mitigate this, a check should be added to the CancelOrderRoute which verifies that the feature is enabled.

Affected Packages

4 total 4 fixed

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

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.3.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-r2vg-hvjm-fg38 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-r2vg-hvjm-fg38 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-r2vg-hvjm-fg38. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

Refunds in general can be enabled through the administration setting `core.cart.enableOrderRefunds` (in the cart panel).Which visually shows and hides the button. However, using a custom crafted request, a customer can still cancel his own orders.As this is not checked inside the route (and also not in the controller): https://github.com/shopware/shopware/blob/trunk/src/Storefront/Controller/AccountOrderController.php#L98 https://github.com/shopware/shopware/blob/trunk/src/Core/Checkout/Order/SalesChannel/CancelOrderRoute.php To mitigate this, a check should be added to the `CancelOrderRoute`

O3 Security · Impact-Aware SCA

Is GHSA-r2vg-hvjm-fg38 in your dependencies?

O3 detects GHSA-r2vg-hvjm-fg38 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