GHSA-65v7-wg35-2qpm: Sylius Resource Bundle Cross-Site Request Forgery vulnerability
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.
Published May 29, 2024
Affected packages
sylius/resource-bundle
- Ecosystem
- Composer (PHP)
- Affected
- >= 1.0.0, < 1.0.17
- Fixed in
- 1.0.17
- Check
composer show sylius/resource-bundle
sylius/resource-bundle
- Ecosystem
- Composer (PHP)
- Affected
- >= 1.1.0, < 1.1.9
- Fixed in
- 1.1.9
- Check
composer show sylius/resource-bundle
sylius/resource-bundle
- Ecosystem
- Composer (PHP)
- Affected
- >= 1.2.0, < 1.2.2
- Fixed in
- 1.2.2
- Check
composer show sylius/resource-bundle
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
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
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
