GHSA-65V7-WG35-2QPM

Sylius 1.0.0 to 1.0.16, 1.1.0 to 1.1.8, 1.2.0 to 1.2.1 versions of AdminBundle and ResourceBundle are affected by this security issue.

This issue has been fixed in Sylius 1.0.17, 1.1.9 and 1.2.2. Development branch for 1.3 release has also been fixed.

Description

The following actions in the admin panel did not require a CSRF token:

• marking order’s payment as completed
• marking order’s payment as refunded
• marking product review as accepted
• marking product review as rejected

Resolution

The issue is fixed by adding a required CSRF token to those actions.

We also fixed ResourceController‘s applyStateMachineTransitionAction method by adding a CSRF token check. If you use that action in the API context, you can disable it by adding csrf_protection: false to its routing configuration

A victim's authenticated browser session is used to submit forged requests to an application that cannot distinguish them from legitimate ones. Typical impact: state-changing actions performed as the victim without their consent.

GHSA-65V7-WG35-2QPM has a CVSS score of 6.5 (Medium). The vector is network-reachable, no privileges required, and user interaction required. 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 (1.0.17, 1.1.9, 1.2.2); upgrading removes the vulnerable code path.

Kodem intelligence

1. What is GHSA-65V7-WG35-2QPM? GHSA-65V7-WG35-2QPM is a medium-severity cross-site request forgery (CSRF) vulnerability in sylius/resource-bundle (composer), affecting versions >= 1.0.0, < 1.0.17. It is fixed in 1.0.17, 1.1.9, 1.2.2. A victim's authenticated browser session is used to submit forged requests to an application that cannot distinguish them from legitimate ones.
2. How severe is GHSA-65V7-WG35-2QPM? GHSA-65V7-WG35-2QPM has a CVSS score of 6.5 (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 versions of sylius/resource-bundle are affected by GHSA-65V7-WG35-2QPM? sylius/resource-bundle (composer) versions >= 1.0.0, < 1.0.17 is affected.
4. Is there a fix for GHSA-65V7-WG35-2QPM? Yes. GHSA-65V7-WG35-2QPM is fixed in 1.0.17, 1.1.9, 1.2.2. Upgrade to this version or later.
5. Is GHSA-65V7-WG35-2QPM exploitable, and should I be worried? Whether GHSA-65V7-WG35-2QPM 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-65V7-WG35-2QPM 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-65V7-WG35-2QPM?
   • Upgrade sylius/resource-bundle to 1.0.17 or later
   • Upgrade sylius/resource-bundle to 1.1.9 or later
   • Upgrade sylius/resource-bundle to 1.2.2 or later

Other vulnerabilities in sylius/resource-bundle