Sylius has a security vulnerability via adjustments API endpoint
Published 17 Jul 2024 · Updated 9 Mar 2026
Is your project on an affected sylius/sylius?
Look after several Laravel or PHP apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Affected packages
- Affected
- >=1.12.0-alpha.1 <1.12.19
- Fixed in
- 1.12.19
composer require sylius/sylius:^1.12.19- Affected
- >=1.13.0-alpha.1 <1.13.4
- Fixed in
- 1.13.4
composer require sylius/sylius:^1.13.4- Affected
- <1.9.12
- Fixed in
- 1.9.12
composer require sylius/sylius:^1.9.12- Affected
- >=1.10.0-alpha.1 <1.10.16
- Fixed in
- 1.10.16
composer require sylius/sylius:^1.10.16- Affected
- >=1.11.0-alpha.1 <1.11.17
- Fixed in
- 1.11.17
composer require sylius/sylius:^1.11.17Details
Impact
A security vulnerability was discovered in the /api/v2/shop/adjustments/{id} endpoint, which retrieves order adjustments based on incremental integer IDs. The vulnerability allows an attacker to enumerate valid adjustment IDs and retrieve order tokens. Using these tokens, an attacker can access guest customer order details - sensitive guest customer information.
Patches
The issue is fixed in versions: 1.9.12, 1.10.16, 1.11.17, 1.12.19, 1.13.4 and above.
The /api/v2/shop/adjustments/{id} will always return 404 status.
Workarounds
Using YAML configuration:
Create config/api_platform/Adjustment.yaml file:
# config/api_platform/Adjustment.yaml
'%sylius.model.adjustment.class%':
itemOperations:
shop_get:
controller: ApiPlatform\Core\Action\NotFoundAction
read: false
output: falseOr using XML configuration:
> Note: This is the only way of disabling the vulnerable endpoint for Sylius 1.9, as YAML configuration is not supported in that version.
Copy the original configuration from vendor:
# create directory if it doesn't exist mkdir -p config/api_platform cp vendor/sylius/sylius/src/Sylius/Bundle/ApiBundle/Resources/config/api_resources/Adjustment.xml config/api_platform
And change the shop_get operation in copied config/api_platform/Adjustment.xml file:
<!-- config/api_platform/Adjustment.xml -->
...
<itemOperation name="shop_get">
<attribute name="method">GET</attribute>
<attribute name="path">/shop/adjustments/{id}</attribute>
<attribute name="controller">ApiPlatform\Core\Action\NotFoundAction</attribute>
<attribute name="read">false</attribute>
<attribute name="output">false</attribute>
</itemOperation>
...Update your API platform paths config if needed so the new configuration file is loaded:
# config/packages/api_platform.yaml
api_platform:
mapping:
paths:
- '%kernel.project_dir%/vendor/sylius/sylius/src/Sylius/Bundle/ApiBundle/Resources/config/api_resources'
...
- '%kernel.project_dir%/config/api_platform'For more information
If you have any questions or comments about this advisory:
- Open an issue in Sylius issues
- Email us at [security@sylius.com](mailto:security@sylius.com)
Is GHSA-55rf-8q29-4g43 in any of your client repos?
Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected sylius/sylius, and gives you the command that fixes it.
More advisories for sylius/sylius
- MediumCVE-2026-53639Sylius: IDOR on Shop Payment Request API endpoints · 9 Jul 2026
- MediumCVE-2026-53638Sylius: Channel-based payment method restriction bypass on shop account orders API endpoint · 9 Jul 2026
- MediumCVE-2026-53637Sylius: Cart FormComponent allows modification or deletion of an already-completed order · 9 Jul 2026
- MediumCVE-2026-31825Sylius has a DQL Injection via API Order Filters · 11 Mar 2026
- HighCVE-2026-31824Sylius has a Promotion Usage Limit Bypass via Race Condition · 11 Mar 2026
- MediumCVE-2026-31823Sylius Vulnerable to Authenticated Stored XSS · 11 Mar 2026
References
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.