Approved changes feed: RSS · Atom
cpe:2.3:a:sylius:sylius:*:*:*:*:*:*:*:*part: a version: * update: *
| Vendor | Sylius (09c994bc-1943-5531-ab63-45ba7c30d733) |
|---|---|
| Product | Sylius (d567aa98-f92e-58b6-bd8f-1473e63c5d90) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
Notes
Imported from purl2cpe mapping
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
pkg:github/sylius/sylius |
purl2cpe | 2026-06-01 10:11:40.831957 |
pkg:sourceforge/sylius.mirror |
purl2cpe | 2026-06-01 10:11:40.831959 |
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2026-108724 |
vulnerable | 2026-11-03 10:18:01.755821 |
Sylius through 2.3.0 Authorization Bypass via Shop API Product-Review Endpoint
MEDIUM (5.3)
Sylius through 2.3.0 contains an authorization bypass vulnerability that allows unauthenticated attackers to read unmoderated and rejected product reviews because the AcceptedExtension filter is not applied to the item operation. Attackers can enumerate sequential ids on GET /api/v2/shop/product-reviews/{id} to retrieve review titles, ratings, comments, timestamps and author first names, bypassing merchant moderation.
Published: 2026-10-11T12:19:33.967Z
Updated: 2026-10-14T13:24:46.304Z Reference links
|
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-53637 |
vulnerable | 2026-09-16 04:33:53.293928 |
Sylius: Cart FormComponent allows modification or deletion of an already-completed order
MEDIUM (6.5)
Sylius is an Open Source eCommerce Framework on Symfony. Versions 2.0.0 through 2.0.17, 2.1.0 through 2.1.14, and 2.2.0 through 2.2.5 contain an improper workflow enforcement vulnerability in the cart `FormComponent`. When an order is completed while its cart page remains open, the stale LiveComponent does not detect the order’s changed state and continues to permit cart actions, allowing an authenticated customer to modify or permanently delete an already completed order. Versions 2.0.18, 2.1.15, and 2.2.6 contain a patch. As a workaround, deployments can copy the patched `FormComponent` into the application's `src/` directory and override the `sylius_shop.twig.component.cart.form` service definition to use that class.
Published: 2026-09-08T22:31:39.758Z
Updated: 2026-09-09T15:37:23.362Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-53638 |
vulnerable | 2026-09-16 04:33:52.974728 |
Sylius: Channel-based payment method restriction bypass on shop account orders API endpoint
MEDIUM (4.3)
Sylius is an Open Source eCommerce Framework on Symfony. Starting in version 2.0.0 and prior to version 2.0.18, 2.1.15, and 2.2.6, an authorization bypass vulnerability exists in the shop account API. The `PATCH /api/v2/shop/account/orders/{tokenValue}/payments/{paymentId}` endpoint, used by an authenticated shop customer to change the payment method of an order that has been placed but not yet paid (state `STATE_NEW`), does not validate that the chosen payment method is enabled for the order's channel. The equivalent checkout endpoint (`PATCH /api/v2/shop/orders/{tokenValue}/payments/{paymentId}`) correctly rejects out-of-channel payment methods with `HTTP 422`; the account endpoint silently accepts them and returns `HTTP 200`. An authenticated customer can therefore assign any globally enabled payment method to their own placed order, including methods that the store operator has explicitly excluded from that channel. The issue is fixed in versions: 2.0.18, 2.1.15, 2.2.6 and above. As a workaround, decorate the `Sylius\Bundle\ApiBundle\Changer\PaymentMethodChangerInterface` service in the application.
Published: 2026-09-08T22:25:26.679Z
Updated: 2026-09-14T12:05:51.544Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-53639 |
vulnerable | 2026-09-16 04:33:52.768275 |
Sylius: IDOR on Shop Payment Request API endpoints
Sylius is an Open Source eCommerce Framework on Symfony. Starting in version 2.0.0 and prior to version 2.0.18, 2.1.15, and 2.2.6, the `GET /api/v2/shop/payment-requests/{hash}` and `PUT /api/v2/shop/payment-requests/{hash}` endpoints look up the payment request solely by the hash from the URL. No ownership check is performed against the authenticated customer or the underlying order. An attacker who obtains a payment request hash can read the payment request and, through the `payment` IRI in the response, recover the underlying order's `tokenValue` (which itself grants access to the full order, items, addresses, customer email, totals); and/or update the payment request payload (e.g. `target_path`, `after_path`). These fields are used by the front-end controller to redirect the user after the payment, so an attacker can flip them to an attacker-controlled URL and intercept the buyer. The hash is a UUID, so it has to be obtained out-of-band (logs, shared links, referrer headers, a co-located client), but once it is known no other credential is required, neither authentication nor knowledge of the order token. The creation endpoint `POST /api/v2/shop/orders/{tokenValue}/payment-requests` shares the same flaw: it resolves the target order solely from the `tokenValue` in the URL without verifying that the caller owns the order. The issue is fixed in versions 2.0.18, 2.1.15, and 2.2.6. As a workaround, add a query extension that filters the `GET` operation; decorate the `PUT` state provider, guard the `POST` creation endpoint with a command-bus middleware, and wire the services.
Published: 2026-09-08T22:22:24.578Z
Updated: 2026-09-09T16:03:44.749Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-31825 |
vulnerable | 2026-06-08 07:57:15.932970 |
Sylius has a DQL Injection via API Order Filters
MEDIUM (5.3)
Sylius is an Open Source eCommerce Framework on Symfony. Sylius API filters ProductPriceOrderFilter and TranslationOrderNameAndLocaleFilter pass user-supplied order direction values directly to Doctrine's orderBy() without validation. An attacker can inject arbitrary DQL. The issue is fixed in versions: 1.9.12, 1.10.16, 1.11.17, 1.12.23, 1.13.15, 1.14.18, 2.0.16, 2.1.12, 2.2.3 and above.
Published: 2026-03-10T21:33:26.471Z
Updated: 2026-03-11T15:19:28.740Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-31824 |
vulnerable | 2026-06-08 07:57:15.932562 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-31823 |
vulnerable | 2026-06-08 07:57:15.932125 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-31822 |
vulnerable | 2026-06-08 07:57:15.931727 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-31821 |
vulnerable | 2026-06-08 07:57:15.931449 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-31820 |
vulnerable | 2026-06-08 07:57:15.931139 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-31819 |
vulnerable | 2026-06-08 07:57:15.930749 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2024-40633 |
vulnerable | 2026-06-08 06:43:52.803431 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2024-34349 |
vulnerable | 2026-06-08 06:37:33.151057 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2022-24749 |
vulnerable | 2026-06-08 05:41:01.544639 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2022-24743 |
vulnerable | 2026-06-08 05:41:01.532565 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2022-24742 |
vulnerable | 2026-06-08 05:41:01.531794 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2022-24733 |
vulnerable | 2026-06-08 05:41:01.474777 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2021-3841 |
vulnerable | 2026-06-08 05:33:54.416842 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2021-32720 |
vulnerable | 2026-06-08 05:32:07.896840 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2020-5218 |
vulnerable | 2026-06-08 05:26:41.521204 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2020-15245 |
vulnerable | 2026-06-08 05:19:25.583490 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2019-16768 |
vulnerable | 2026-06-08 05:13:09.355698 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2019-12186 |
vulnerable | 2026-06-08 05:12:38.674356 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.
Inspect record JSON
Open this panel to browse, search, copy or download the JSON record.