{"items":[{"id":"NVI-00008296","kind":"vulnerability","title":"Sylius: Channel-based payment method restriction bypass on shop account orders API endpoint","revision":3,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-6955-hrm5-c4qp","CVE-2026-53638"],"plain_summary":"OSV carries this publisher advisory for sylius/sylius, sylius/sylius, sylius/sylius. This is an aggregated source copy; consult the original publisher and compare update dates.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"The original advisory lists fixed boundaries 2.0.18 for sylius/sylius. Confirm the publisher’s latest guidance.","source_ids":["sr-fdbd7917e6845cbf8086e1b47fcd2d4c"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 2.1.15 for sylius/sylius. Confirm the publisher’s latest guidance.","source_ids":["sr-fdbd7917e6845cbf8086e1b47fcd2d4c"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 2.2.6 for sylius/sylius. Confirm the publisher’s latest guidance.","source_ids":["sr-fdbd7917e6845cbf8086e1b47fcd2d4c"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-2b0fd4e51354ff3c05e16c8f5156c34c"],"action_type":"investigate","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[{"kind":"EPSS","as_of":"2026-11-02T12:00:30.000Z","value":"0.284%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.2096. Missing scores are unknown.","source_id":"sr-2b0fd4e51354ff3c05e16c8f5156c34c"}],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-fdbd7917e6845cbf8086e1b47fcd2d4c","url":"https://github.com/advisories/GHSA-6955-hrm5-c4qp","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-6955-hrm5-c4qp","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:41:59.933Z"},{"id":"sr-2b0fd4e51354ff3c05e16c8f5156c34c","url":"https://www.first.org/epss/data.html","basis":"official_catalog","notes":"FIRST EPSS; probability of exploitation in the next 30 days, not local compromise. Dataset date/model retained; FIRST services terms apply.","title":"CVE-2026-53638","publisher":"FIRST EPSS","observed_at":"2026-11-02T20:15:58.857Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-fdbd7917e6845cbf8086e1b47fcd2d4c"],"technology":"sylius/sylius","known_exclusions":[],"conditions_summary":"### Impact\nAn 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`.\n\nAn 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. \n\n### Patches\nThe issue is fixed in versions: 2.0.18, 2.1.15, 2.2.6 and above.\n\n### Workarounds\nIf users cannot bump Sylius right now, decorate the `Sylius\\Bundle\\ApiBundle\\Changer\\PaymentMethodChangerInterface` service in their applications. \n\n#### Step 1. Create the decorator\n\n`src/Decorator/ChannelCheckingPaymentMethodChanger.php`:\n\n```php\n<?php\n\ndeclare(strict_types=1);\n\nnamespa","public_affected_ranges":["ECOSYSTEM: introduced 2.0.0; fixed 2.0.18"]},{"certainty":"source_listed","source_ids":["sr-fdbd7917e6845cbf8086e1b47fcd2d4c"],"technology":"sylius/sylius","known_exclusions":[],"conditions_summary":"### Impact\nAn 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`.\n\nAn 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. \n\n### Patches\nThe issue is fixed in versions: 2.0.18, 2.1.15, 2.2.6 and above.\n\n### Workarounds\nIf users cannot bump Sylius right now, decorate the `Sylius\\Bundle\\ApiBundle\\Changer\\PaymentMethodChangerInterface` service in their applications. \n\n#### Step 1. Create the decorator\n\n`src/Decorator/ChannelCheckingPaymentMethodChanger.php`:\n\n```php\n<?php\n\ndeclare(strict_types=1);\n\nnamespa","public_affected_ranges":["ECOSYSTEM: introduced 2.1.0; fixed 2.1.15"]},{"certainty":"source_listed","source_ids":["sr-fdbd7917e6845cbf8086e1b47fcd2d4c"],"technology":"sylius/sylius","known_exclusions":[],"conditions_summary":"### Impact\nAn 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`.\n\nAn 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. \n\n### Patches\nThe issue is fixed in versions: 2.0.18, 2.1.15, 2.2.6 and above.\n\n### Workarounds\nIf users cannot bump Sylius right now, decorate the `Sylius\\Bundle\\ApiBundle\\Changer\\PaymentMethodChangerInterface` service in their applications. \n\n#### Step 1. Create the decorator\n\n`src/Decorator/ChannelCheckingPaymentMethodChanger.php`:\n\n```php\n<?php\n\ndeclare(strict_types=1);\n\nnamespa","public_affected_ranges":["ECOSYSTEM: introduced 2.2.0; fixed 2.2.6"]}],"null_published_at":"2026-11-08T19:53:38.913Z","source_updated_at":"2026-07-09T21:26:41.702Z","source_disclosed_at":"2026-07-09T21:03:46.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"Dated EPSS estimate updated; this is not a new disclosure or proof of exploitation.","null_first_observed_at":"2026-10-31T21:41:59.933Z"},{"id":"NVI-00008296","kind":"vulnerability","title":"Sylius: Channel-based payment method restriction bypass on shop account orders API endpoint","revision":2,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-6955-hrm5-c4qp","CVE-2026-53638"],"plain_summary":"OSV carries this publisher advisory for sylius/sylius, sylius/sylius, sylius/sylius. This is an aggregated source copy; consult the original publisher and compare update dates.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"The original advisory lists fixed boundaries 2.0.18 for sylius/sylius. Confirm the publisher’s latest guidance.","source_ids":["sr-fdbd7917e6845cbf8086e1b47fcd2d4c"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 2.1.15 for sylius/sylius. Confirm the publisher’s latest guidance.","source_ids":["sr-fdbd7917e6845cbf8086e1b47fcd2d4c"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 2.2.6 for sylius/sylius. Confirm the publisher’s latest guidance.","source_ids":["sr-fdbd7917e6845cbf8086e1b47fcd2d4c"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-1bb375e451e46c98481174a85a1533c4"],"action_type":"investigate","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[{"kind":"EPSS","as_of":"2026-11-01T12:00:16.000Z","value":"0.284%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.20975. Missing scores are unknown.","source_id":"sr-1bb375e451e46c98481174a85a1533c4"}],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-fdbd7917e6845cbf8086e1b47fcd2d4c","url":"https://github.com/advisories/GHSA-6955-hrm5-c4qp","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-6955-hrm5-c4qp","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:41:59.933Z"},{"id":"sr-1bb375e451e46c98481174a85a1533c4","url":"https://www.first.org/epss/data.html","basis":"official_catalog","notes":"FIRST EPSS; probability of exploitation in the next 30 days, not local compromise. Dataset date/model retained; FIRST services terms apply.","title":"CVE-2026-53638","publisher":"FIRST EPSS","observed_at":"2026-11-01T14:28:32.282Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-fdbd7917e6845cbf8086e1b47fcd2d4c"],"technology":"sylius/sylius","known_exclusions":[],"conditions_summary":"### Impact\nAn 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`.\n\nAn 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. \n\n### Patches\nThe issue is fixed in versions: 2.0.18, 2.1.15, 2.2.6 and above.\n\n### Workarounds\nIf users cannot bump Sylius right now, decorate the `Sylius\\Bundle\\ApiBundle\\Changer\\PaymentMethodChangerInterface` service in their applications. \n\n#### Step 1. Create the decorator\n\n`src/Decorator/ChannelCheckingPaymentMethodChanger.php`:\n\n```php\n<?php\n\ndeclare(strict_types=1);\n\nnamespa","public_affected_ranges":["ECOSYSTEM: introduced 2.0.0; fixed 2.0.18"]},{"certainty":"source_listed","source_ids":["sr-fdbd7917e6845cbf8086e1b47fcd2d4c"],"technology":"sylius/sylius","known_exclusions":[],"conditions_summary":"### Impact\nAn 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`.\n\nAn 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. \n\n### Patches\nThe issue is fixed in versions: 2.0.18, 2.1.15, 2.2.6 and above.\n\n### Workarounds\nIf users cannot bump Sylius right now, decorate the `Sylius\\Bundle\\ApiBundle\\Changer\\PaymentMethodChangerInterface` service in their applications. \n\n#### Step 1. Create the decorator\n\n`src/Decorator/ChannelCheckingPaymentMethodChanger.php`:\n\n```php\n<?php\n\ndeclare(strict_types=1);\n\nnamespa","public_affected_ranges":["ECOSYSTEM: introduced 2.1.0; fixed 2.1.15"]},{"certainty":"source_listed","source_ids":["sr-fdbd7917e6845cbf8086e1b47fcd2d4c"],"technology":"sylius/sylius","known_exclusions":[],"conditions_summary":"### Impact\nAn 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`.\n\nAn 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. \n\n### Patches\nThe issue is fixed in versions: 2.0.18, 2.1.15, 2.2.6 and above.\n\n### Workarounds\nIf users cannot bump Sylius right now, decorate the `Sylius\\Bundle\\ApiBundle\\Changer\\PaymentMethodChangerInterface` service in their applications. \n\n#### Step 1. Create the decorator\n\n`src/Decorator/ChannelCheckingPaymentMethodChanger.php`:\n\n```php\n<?php\n\ndeclare(strict_types=1);\n\nnamespa","public_affected_ranges":["ECOSYSTEM: introduced 2.2.0; fixed 2.2.6"]}],"null_published_at":"2026-11-04T18:04:03.101Z","source_updated_at":"2026-07-09T21:26:41.702Z","source_disclosed_at":"2026-07-09T21:03:46.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"Dated EPSS estimate updated; this is not a new disclosure or proof of exploitation.","null_first_observed_at":"2026-10-31T21:41:59.933Z"},{"id":"NVI-00008296","kind":"vulnerability","title":"Sylius: Channel-based payment method restriction bypass on shop account orders API endpoint","revision":1,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-6955-hrm5-c4qp","CVE-2026-53638"],"plain_summary":"OSV carries this publisher advisory for sylius/sylius, sylius/sylius, sylius/sylius. This is an aggregated source copy; consult the original publisher and compare update dates.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"The original advisory lists fixed boundaries 2.0.18 for sylius/sylius. Confirm the publisher’s latest guidance.","source_ids":["sr-fdbd7917e6845cbf8086e1b47fcd2d4c"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 2.1.15 for sylius/sylius. Confirm the publisher’s latest guidance.","source_ids":["sr-fdbd7917e6845cbf8086e1b47fcd2d4c"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 2.2.6 for sylius/sylius. Confirm the publisher’s latest guidance.","source_ids":["sr-fdbd7917e6845cbf8086e1b47fcd2d4c"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-fdbd7917e6845cbf8086e1b47fcd2d4c","url":"https://github.com/advisories/GHSA-6955-hrm5-c4qp","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-6955-hrm5-c4qp","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:41:59.933Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-fdbd7917e6845cbf8086e1b47fcd2d4c"],"technology":"sylius/sylius","known_exclusions":[],"conditions_summary":"### Impact\nAn 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`.\n\nAn 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. \n\n### Patches\nThe issue is fixed in versions: 2.0.18, 2.1.15, 2.2.6 and above.\n\n### Workarounds\nIf users cannot bump Sylius right now, decorate the `Sylius\\Bundle\\ApiBundle\\Changer\\PaymentMethodChangerInterface` service in their applications. \n\n#### Step 1. Create the decorator\n\n`src/Decorator/ChannelCheckingPaymentMethodChanger.php`:\n\n```php\n<?php\n\ndeclare(strict_types=1);\n\nnamespa","public_affected_ranges":["ECOSYSTEM: introduced 2.0.0; fixed 2.0.18"]},{"certainty":"source_listed","source_ids":["sr-fdbd7917e6845cbf8086e1b47fcd2d4c"],"technology":"sylius/sylius","known_exclusions":[],"conditions_summary":"### Impact\nAn 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`.\n\nAn 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. \n\n### Patches\nThe issue is fixed in versions: 2.0.18, 2.1.15, 2.2.6 and above.\n\n### Workarounds\nIf users cannot bump Sylius right now, decorate the `Sylius\\Bundle\\ApiBundle\\Changer\\PaymentMethodChangerInterface` service in their applications. \n\n#### Step 1. Create the decorator\n\n`src/Decorator/ChannelCheckingPaymentMethodChanger.php`:\n\n```php\n<?php\n\ndeclare(strict_types=1);\n\nnamespa","public_affected_ranges":["ECOSYSTEM: introduced 2.1.0; fixed 2.1.15"]},{"certainty":"source_listed","source_ids":["sr-fdbd7917e6845cbf8086e1b47fcd2d4c"],"technology":"sylius/sylius","known_exclusions":[],"conditions_summary":"### Impact\nAn 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`.\n\nAn 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. \n\n### Patches\nThe issue is fixed in versions: 2.0.18, 2.1.15, 2.2.6 and above.\n\n### Workarounds\nIf users cannot bump Sylius right now, decorate the `Sylius\\Bundle\\ApiBundle\\Changer\\PaymentMethodChangerInterface` service in their applications. \n\n#### Step 1. Create the decorator\n\n`src/Decorator/ChannelCheckingPaymentMethodChanger.php`:\n\n```php\n<?php\n\ndeclare(strict_types=1);\n\nnamespa","public_affected_ranges":["ECOSYSTEM: introduced 2.2.0; fixed 2.2.6"]}],"null_published_at":"2026-10-31T22:13:22.838Z","source_updated_at":"2026-07-09T21:26:41.702Z","source_disclosed_at":"2026-07-09T21:03:46.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"First indexed by Null; source disclosure date is shown separately.","null_first_observed_at":"2026-10-31T21:41:59.933Z"}],"next_cursor":null,"snapshot_revision":"42594"}