{"items":[{"id":"NVI-00005396","kind":"vulnerability","title":"List of order ids, number, items total and token value exposed for unauthorized uses via new API","revision":2,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-rpxh-vg2x-526v","CVE-2021-32720"],"plain_summary":"OSV carries this publisher advisory for 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 1.9.5 for sylius/sylius. Confirm the publisher’s latest guidance.","source_ids":["sr-8db20579db6c1ab4caeffaeb143a9473"],"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-55afa77b09296735466f12e3a62aa242"],"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-10-31T12:00:27.000Z","value":"0.881%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.59132. Missing scores are unknown.","source_id":"sr-55afa77b09296735466f12e3a62aa242"}],"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-8db20579db6c1ab4caeffaeb143a9473","url":"https://github.com/advisories/GHSA-rpxh-vg2x-526v","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-rpxh-vg2x-526v","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:42:41.365Z"},{"id":"sr-55afa77b09296735466f12e3a62aa242","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-2021-32720","publisher":"FIRST EPSS","observed_at":"2026-10-31T22:06:03.704Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-8db20579db6c1ab4caeffaeb143a9473"],"technology":"sylius/sylius","known_exclusions":[],"conditions_summary":"### Impact\n\nPart of the details (order ID, order number, items total, and token value) of all placed orders were exposed to unauthorized users. If exploited properly, a few additional information like the number of items in the cart and the date of the shipping may be fetched as well. This data seems to not be crucial nor is personal data, however, could be used for sociotechnical attacks or may expose a few details about shop condition to the third parties. The data possible to aggregate are the number of processed orders or their value in the moment of time. \n\n### Patches\n\nThe problem has been patched at Sylius 1.9.5 and 1.10.0\n\n### Workarounds\nThere are a few ways to fix this without updating the code. \n\nThe first possible solution is to hide the problematic endpoints behind the firewall from not logged in users. In order to achieve it one has to add the configuration in `config/packages/security.yaml`:\n```yaml\n    access_control:\n        # ... \n        - { path: \"%sylius.security.new_api_shop_regex%/orders\", role: IS_AUTHENTICATED_ANONYMOUSLY, methods: [POST] }\n        - { path: \"%sylius.security.new_api_shop_regex%/orders\", role: ROLE_USER, methods: [GET] }\n```\nThis would put ","public_affected_ranges":["ECOSYSTEM: introduced 1.9.0; fixed 1.9.5"]}],"null_published_at":"2026-11-01T01:04:04.847Z","source_updated_at":"2026-07-08T06:28:43.151Z","source_disclosed_at":"2021-06-29T03:12:04.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:42:41.365Z"},{"id":"NVI-00005396","kind":"vulnerability","title":"List of order ids, number, items total and token value exposed for unauthorized uses via new API","revision":1,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-rpxh-vg2x-526v","CVE-2021-32720"],"plain_summary":"OSV carries this publisher advisory for 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 1.9.5 for sylius/sylius. Confirm the publisher’s latest guidance.","source_ids":["sr-8db20579db6c1ab4caeffaeb143a9473"],"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-8db20579db6c1ab4caeffaeb143a9473","url":"https://github.com/advisories/GHSA-rpxh-vg2x-526v","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-rpxh-vg2x-526v","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:42:41.365Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-8db20579db6c1ab4caeffaeb143a9473"],"technology":"sylius/sylius","known_exclusions":[],"conditions_summary":"### Impact\n\nPart of the details (order ID, order number, items total, and token value) of all placed orders were exposed to unauthorized users. If exploited properly, a few additional information like the number of items in the cart and the date of the shipping may be fetched as well. This data seems to not be crucial nor is personal data, however, could be used for sociotechnical attacks or may expose a few details about shop condition to the third parties. The data possible to aggregate are the number of processed orders or their value in the moment of time. \n\n### Patches\n\nThe problem has been patched at Sylius 1.9.5 and 1.10.0\n\n### Workarounds\nThere are a few ways to fix this without updating the code. \n\nThe first possible solution is to hide the problematic endpoints behind the firewall from not logged in users. In order to achieve it one has to add the configuration in `config/packages/security.yaml`:\n```yaml\n    access_control:\n        # ... \n        - { path: \"%sylius.security.new_api_shop_regex%/orders\", role: IS_AUTHENTICATED_ANONYMOUSLY, methods: [POST] }\n        - { path: \"%sylius.security.new_api_shop_regex%/orders\", role: ROLE_USER, methods: [GET] }\n```\nThis would put ","public_affected_ranges":["ECOSYSTEM: introduced 1.9.0; fixed 1.9.5"]}],"null_published_at":"2026-10-31T22:13:01.463Z","source_updated_at":"2026-07-08T06:28:43.151Z","source_disclosed_at":"2021-06-29T03:12:04.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:42:41.365Z"}],"next_cursor":null,"snapshot_revision":"42594"}