GHSA-945h-6vcv-pc8h is a medium-severity (CVSS 6.5) vulnerability in sylius/admin-bundle. A fix is available for sylius/admin-bundle — see the affected versions and patch details below.
Sylius Admin Bundle Cross-Site Request Forgery vulnerability
Real-World Exposure
sylius/admin-bundle🐘sylius/admin-bundle🐘sylius/admin-bundleReal-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
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
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | sylius/admin-bundle | ≥ 1.0.0&&< 1.0.17 | 1.0.17composer require sylius/admin-bundle:^1.0.17 |
| 🐘Packagist | sylius/admin-bundle | ≥ 1.1.0&&< 1.1.9 | 1.1.9composer require sylius/admin-bundle:^1.1.9 |
| 🐘Packagist | sylius/admin-bundle | ≥ 1.2.0&&< 1.2.2 | 1.2.2composer require sylius/admin-bundle:^1.2.2 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for sylius/admin-bundle, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update sylius/admin-bundle to 1.0.17 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-945h-6vcv-pc8h 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 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-945h-6vcv-pc8h can be triaged on real exposure rather than presence alone.
Tailored to GHSA-945h-6vcv-pc8h. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-945h-6vcv-pc8h in your dependencies?
O3 Security finds GHSA-945h-6vcv-pc8h across Packagist dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.