{"items":[{"id":"NVI-00005180","kind":"vulnerability","title":"Sylius has a security vulnerability via adjustments API endpoint","revision":4,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected.","NVD lastModified does not establish freshness of every associated CPE record."],"lifecycle":"active","identifiers":["GHSA-55rf-8q29-4g43","CVE-2024-40633"],"plain_summary":"OSV carries this publisher advisory for sylius/sylius, sylius/sylius, 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 1.12.19 for sylius/sylius. Confirm the publisher’s latest guidance.","source_ids":["sr-85d4062b4bb64cbae3093a74e97f9288"],"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 1.13.4 for sylius/sylius. Confirm the publisher’s latest guidance.","source_ids":["sr-85d4062b4bb64cbae3093a74e97f9288"],"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 1.9.12 for sylius/sylius. Confirm the publisher’s latest guidance.","source_ids":["sr-85d4062b4bb64cbae3093a74e97f9288"],"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 1.10.16 for sylius/sylius. Confirm the publisher’s latest guidance.","source_ids":["sr-85d4062b4bb64cbae3093a74e97f9288"],"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 1.11.17 for sylius/sylius. Confirm the publisher’s latest guidance.","source_ids":["sr-85d4062b4bb64cbae3093a74e97f9288"],"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-1804251ea22ba75b02186b02da535a28"],"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":"CVSS","as_of":"2026-06-17T07:46:12.587Z","value":"5.3 MEDIUM (3.1)","meaning":"security-advisories@github.com severity; no combined Null risk score.","source_id":"sr-88a45f098933e9ecec585e2b3e5c2946"},{"kind":"EPSS","as_of":"2026-11-02T12:00:30.000Z","value":"0.380%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.32008. Missing scores are unknown.","source_id":"sr-1804251ea22ba75b02186b02da535a28"}],"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-85d4062b4bb64cbae3093a74e97f9288","url":"https://github.com/advisories/GHSA-55rf-8q29-4g43","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-55rf-8q29-4g43","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:41:49.678Z"},{"id":"sr-88a45f098933e9ecec585e2b3e5c2946","url":"https://nvd.nist.gov/vuln/detail/CVE-2024-40633","basis":"official_catalog","notes":"This product uses data from the NVD API but is not endorsed or certified by the NVD.","title":"CVE-2024-40633","publisher":"NIST National Vulnerability Database","observed_at":"2026-11-01T00:59:28.975Z"},{"id":"sr-1804251ea22ba75b02186b02da535a28","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-2024-40633","publisher":"FIRST EPSS","observed_at":"2026-11-02T20:15:58.826Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-85d4062b4bb64cbae3093a74e97f9288"],"technology":"sylius/sylius","known_exclusions":[],"conditions_summary":"### Impact\nA 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.\n\n### Patches\nThe issue is fixed in versions: 1.9.12, 1.10.16, 1.11.17, 1.12.19, 1.13.4 and above.\nThe `/api/v2/shop/adjustments/{id}` will always return `404` status.\n\n### Workarounds\n\nUsing YAML configuration:\n\nCreate `config/api_platform/Adjustment.yaml` file:\n\n```yaml\n# config/api_platform/Adjustment.yaml\n\n'%sylius.model.adjustment.class%':\n    itemOperations:\n        shop_get:\n            controller: ApiPlatform\\Core\\Action\\NotFoundAction\n            read: false\n            output: false\n```\n\nOr using XML configuration:\n\n> Note: This is the only way of disabling the vulnerable endpoint for Sylius 1.9, as YAML configuration is not supported in that version.\n\nCopy the original configuration from vendor:\n\n```bash\n# create directory if it doesn't exist\nmkdir -p config/api_platform\n\ncp vendor/sylius/sylius/src/S","public_affected_ranges":["ECOSYSTEM: introduced 1.12.0-alpha.1; fixed 1.12.19"]},{"certainty":"source_listed","source_ids":["sr-85d4062b4bb64cbae3093a74e97f9288"],"technology":"sylius/sylius","known_exclusions":[],"conditions_summary":"### Impact\nA 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.\n\n### Patches\nThe issue is fixed in versions: 1.9.12, 1.10.16, 1.11.17, 1.12.19, 1.13.4 and above.\nThe `/api/v2/shop/adjustments/{id}` will always return `404` status.\n\n### Workarounds\n\nUsing YAML configuration:\n\nCreate `config/api_platform/Adjustment.yaml` file:\n\n```yaml\n# config/api_platform/Adjustment.yaml\n\n'%sylius.model.adjustment.class%':\n    itemOperations:\n        shop_get:\n            controller: ApiPlatform\\Core\\Action\\NotFoundAction\n            read: false\n            output: false\n```\n\nOr using XML configuration:\n\n> Note: This is the only way of disabling the vulnerable endpoint for Sylius 1.9, as YAML configuration is not supported in that version.\n\nCopy the original configuration from vendor:\n\n```bash\n# create directory if it doesn't exist\nmkdir -p config/api_platform\n\ncp vendor/sylius/sylius/src/S","public_affected_ranges":["ECOSYSTEM: introduced 1.13.0-alpha.1; fixed 1.13.4"]},{"certainty":"source_listed","source_ids":["sr-85d4062b4bb64cbae3093a74e97f9288"],"technology":"sylius/sylius","known_exclusions":[],"conditions_summary":"### Impact\nA 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.\n\n### Patches\nThe issue is fixed in versions: 1.9.12, 1.10.16, 1.11.17, 1.12.19, 1.13.4 and above.\nThe `/api/v2/shop/adjustments/{id}` will always return `404` status.\n\n### Workarounds\n\nUsing YAML configuration:\n\nCreate `config/api_platform/Adjustment.yaml` file:\n\n```yaml\n# config/api_platform/Adjustment.yaml\n\n'%sylius.model.adjustment.class%':\n    itemOperations:\n        shop_get:\n            controller: ApiPlatform\\Core\\Action\\NotFoundAction\n            read: false\n            output: false\n```\n\nOr using XML configuration:\n\n> Note: This is the only way of disabling the vulnerable endpoint for Sylius 1.9, as YAML configuration is not supported in that version.\n\nCopy the original configuration from vendor:\n\n```bash\n# create directory if it doesn't exist\nmkdir -p config/api_platform\n\ncp vendor/sylius/sylius/src/S","public_affected_ranges":["ECOSYSTEM: introduced 0; fixed 1.9.12"]},{"certainty":"source_listed","source_ids":["sr-85d4062b4bb64cbae3093a74e97f9288"],"technology":"sylius/sylius","known_exclusions":[],"conditions_summary":"### Impact\nA 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.\n\n### Patches\nThe issue is fixed in versions: 1.9.12, 1.10.16, 1.11.17, 1.12.19, 1.13.4 and above.\nThe `/api/v2/shop/adjustments/{id}` will always return `404` status.\n\n### Workarounds\n\nUsing YAML configuration:\n\nCreate `config/api_platform/Adjustment.yaml` file:\n\n```yaml\n# config/api_platform/Adjustment.yaml\n\n'%sylius.model.adjustment.class%':\n    itemOperations:\n        shop_get:\n            controller: ApiPlatform\\Core\\Action\\NotFoundAction\n            read: false\n            output: false\n```\n\nOr using XML configuration:\n\n> Note: This is the only way of disabling the vulnerable endpoint for Sylius 1.9, as YAML configuration is not supported in that version.\n\nCopy the original configuration from vendor:\n\n```bash\n# create directory if it doesn't exist\nmkdir -p config/api_platform\n\ncp vendor/sylius/sylius/src/S","public_affected_ranges":["ECOSYSTEM: introduced 1.10.0-alpha.1; fixed 1.10.16"]},{"certainty":"source_listed","source_ids":["sr-85d4062b4bb64cbae3093a74e97f9288"],"technology":"sylius/sylius","known_exclusions":[],"conditions_summary":"### Impact\nA 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.\n\n### Patches\nThe issue is fixed in versions: 1.9.12, 1.10.16, 1.11.17, 1.12.19, 1.13.4 and above.\nThe `/api/v2/shop/adjustments/{id}` will always return `404` status.\n\n### Workarounds\n\nUsing YAML configuration:\n\nCreate `config/api_platform/Adjustment.yaml` file:\n\n```yaml\n# config/api_platform/Adjustment.yaml\n\n'%sylius.model.adjustment.class%':\n    itemOperations:\n        shop_get:\n            controller: ApiPlatform\\Core\\Action\\NotFoundAction\n            read: false\n            output: false\n```\n\nOr using XML configuration:\n\n> Note: This is the only way of disabling the vulnerable endpoint for Sylius 1.9, as YAML configuration is not supported in that version.\n\nCopy the original configuration from vendor:\n\n```bash\n# create directory if it doesn't exist\nmkdir -p config/api_platform\n\ncp vendor/sylius/sylius/src/S","public_affected_ranges":["ECOSYSTEM: introduced 1.11.0-alpha.1; fixed 1.11.17"]}],"null_published_at":"2026-11-06T00:30:00.624Z","source_updated_at":"2026-03-09T16:01:31.134Z","source_disclosed_at":"2024-07-17T14:32:18.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:49.678Z"},{"id":"NVI-00005180","kind":"vulnerability","title":"Sylius has a security vulnerability via adjustments API endpoint","revision":3,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected.","NVD lastModified does not establish freshness of every associated CPE record."],"lifecycle":"active","identifiers":["GHSA-55rf-8q29-4g43","CVE-2024-40633"],"plain_summary":"OSV carries this publisher advisory for sylius/sylius, sylius/sylius, 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 1.12.19 for sylius/sylius. Confirm the publisher’s latest guidance.","source_ids":["sr-85d4062b4bb64cbae3093a74e97f9288"],"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 1.13.4 for sylius/sylius. Confirm the publisher’s latest guidance.","source_ids":["sr-85d4062b4bb64cbae3093a74e97f9288"],"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 1.9.12 for sylius/sylius. Confirm the publisher’s latest guidance.","source_ids":["sr-85d4062b4bb64cbae3093a74e97f9288"],"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 1.10.16 for sylius/sylius. Confirm the publisher’s latest guidance.","source_ids":["sr-85d4062b4bb64cbae3093a74e97f9288"],"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 1.11.17 for sylius/sylius. Confirm the publisher’s latest guidance.","source_ids":["sr-85d4062b4bb64cbae3093a74e97f9288"],"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-56b49d39726116356cf7adc9bc5eef29"],"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":"CVSS","as_of":"2026-06-17T07:46:12.587Z","value":"5.3 MEDIUM (3.1)","meaning":"security-advisories@github.com severity; no combined Null risk score.","source_id":"sr-88a45f098933e9ecec585e2b3e5c2946"},{"kind":"EPSS","as_of":"2026-10-31T12:00:27.000Z","value":"0.380%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.32022. Missing scores are unknown.","source_id":"sr-56b49d39726116356cf7adc9bc5eef29"}],"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-85d4062b4bb64cbae3093a74e97f9288","url":"https://github.com/advisories/GHSA-55rf-8q29-4g43","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-55rf-8q29-4g43","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:41:49.678Z"},{"id":"sr-88a45f098933e9ecec585e2b3e5c2946","url":"https://nvd.nist.gov/vuln/detail/CVE-2024-40633","basis":"official_catalog","notes":"This product uses data from the NVD API but is not endorsed or certified by the NVD.","title":"CVE-2024-40633","publisher":"NIST National Vulnerability Database","observed_at":"2026-11-01T00:59:28.975Z"},{"id":"sr-56b49d39726116356cf7adc9bc5eef29","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-2024-40633","publisher":"FIRST EPSS","observed_at":"2026-10-31T22:06:15.368Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-85d4062b4bb64cbae3093a74e97f9288"],"technology":"sylius/sylius","known_exclusions":[],"conditions_summary":"### Impact\nA 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.\n\n### Patches\nThe issue is fixed in versions: 1.9.12, 1.10.16, 1.11.17, 1.12.19, 1.13.4 and above.\nThe `/api/v2/shop/adjustments/{id}` will always return `404` status.\n\n### Workarounds\n\nUsing YAML configuration:\n\nCreate `config/api_platform/Adjustment.yaml` file:\n\n```yaml\n# config/api_platform/Adjustment.yaml\n\n'%sylius.model.adjustment.class%':\n    itemOperations:\n        shop_get:\n            controller: ApiPlatform\\Core\\Action\\NotFoundAction\n            read: false\n            output: false\n```\n\nOr using XML configuration:\n\n> Note: This is the only way of disabling the vulnerable endpoint for Sylius 1.9, as YAML configuration is not supported in that version.\n\nCopy the original configuration from vendor:\n\n```bash\n# create directory if it doesn't exist\nmkdir -p config/api_platform\n\ncp vendor/sylius/sylius/src/S","public_affected_ranges":["ECOSYSTEM: introduced 1.12.0-alpha.1; fixed 1.12.19"]},{"certainty":"source_listed","source_ids":["sr-85d4062b4bb64cbae3093a74e97f9288"],"technology":"sylius/sylius","known_exclusions":[],"conditions_summary":"### Impact\nA 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.\n\n### Patches\nThe issue is fixed in versions: 1.9.12, 1.10.16, 1.11.17, 1.12.19, 1.13.4 and above.\nThe `/api/v2/shop/adjustments/{id}` will always return `404` status.\n\n### Workarounds\n\nUsing YAML configuration:\n\nCreate `config/api_platform/Adjustment.yaml` file:\n\n```yaml\n# config/api_platform/Adjustment.yaml\n\n'%sylius.model.adjustment.class%':\n    itemOperations:\n        shop_get:\n            controller: ApiPlatform\\Core\\Action\\NotFoundAction\n            read: false\n            output: false\n```\n\nOr using XML configuration:\n\n> Note: This is the only way of disabling the vulnerable endpoint for Sylius 1.9, as YAML configuration is not supported in that version.\n\nCopy the original configuration from vendor:\n\n```bash\n# create directory if it doesn't exist\nmkdir -p config/api_platform\n\ncp vendor/sylius/sylius/src/S","public_affected_ranges":["ECOSYSTEM: introduced 1.13.0-alpha.1; fixed 1.13.4"]},{"certainty":"source_listed","source_ids":["sr-85d4062b4bb64cbae3093a74e97f9288"],"technology":"sylius/sylius","known_exclusions":[],"conditions_summary":"### Impact\nA 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.\n\n### Patches\nThe issue is fixed in versions: 1.9.12, 1.10.16, 1.11.17, 1.12.19, 1.13.4 and above.\nThe `/api/v2/shop/adjustments/{id}` will always return `404` status.\n\n### Workarounds\n\nUsing YAML configuration:\n\nCreate `config/api_platform/Adjustment.yaml` file:\n\n```yaml\n# config/api_platform/Adjustment.yaml\n\n'%sylius.model.adjustment.class%':\n    itemOperations:\n        shop_get:\n            controller: ApiPlatform\\Core\\Action\\NotFoundAction\n            read: false\n            output: false\n```\n\nOr using XML configuration:\n\n> Note: This is the only way of disabling the vulnerable endpoint for Sylius 1.9, as YAML configuration is not supported in that version.\n\nCopy the original configuration from vendor:\n\n```bash\n# create directory if it doesn't exist\nmkdir -p config/api_platform\n\ncp vendor/sylius/sylius/src/S","public_affected_ranges":["ECOSYSTEM: introduced 0; fixed 1.9.12"]},{"certainty":"source_listed","source_ids":["sr-85d4062b4bb64cbae3093a74e97f9288"],"technology":"sylius/sylius","known_exclusions":[],"conditions_summary":"### Impact\nA 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.\n\n### Patches\nThe issue is fixed in versions: 1.9.12, 1.10.16, 1.11.17, 1.12.19, 1.13.4 and above.\nThe `/api/v2/shop/adjustments/{id}` will always return `404` status.\n\n### Workarounds\n\nUsing YAML configuration:\n\nCreate `config/api_platform/Adjustment.yaml` file:\n\n```yaml\n# config/api_platform/Adjustment.yaml\n\n'%sylius.model.adjustment.class%':\n    itemOperations:\n        shop_get:\n            controller: ApiPlatform\\Core\\Action\\NotFoundAction\n            read: false\n            output: false\n```\n\nOr using XML configuration:\n\n> Note: This is the only way of disabling the vulnerable endpoint for Sylius 1.9, as YAML configuration is not supported in that version.\n\nCopy the original configuration from vendor:\n\n```bash\n# create directory if it doesn't exist\nmkdir -p config/api_platform\n\ncp vendor/sylius/sylius/src/S","public_affected_ranges":["ECOSYSTEM: introduced 1.10.0-alpha.1; fixed 1.10.16"]},{"certainty":"source_listed","source_ids":["sr-85d4062b4bb64cbae3093a74e97f9288"],"technology":"sylius/sylius","known_exclusions":[],"conditions_summary":"### Impact\nA 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.\n\n### Patches\nThe issue is fixed in versions: 1.9.12, 1.10.16, 1.11.17, 1.12.19, 1.13.4 and above.\nThe `/api/v2/shop/adjustments/{id}` will always return `404` status.\n\n### Workarounds\n\nUsing YAML configuration:\n\nCreate `config/api_platform/Adjustment.yaml` file:\n\n```yaml\n# config/api_platform/Adjustment.yaml\n\n'%sylius.model.adjustment.class%':\n    itemOperations:\n        shop_get:\n            controller: ApiPlatform\\Core\\Action\\NotFoundAction\n            read: false\n            output: false\n```\n\nOr using XML configuration:\n\n> Note: This is the only way of disabling the vulnerable endpoint for Sylius 1.9, as YAML configuration is not supported in that version.\n\nCopy the original configuration from vendor:\n\n```bash\n# create directory if it doesn't exist\nmkdir -p config/api_platform\n\ncp vendor/sylius/sylius/src/S","public_affected_ranges":["ECOSYSTEM: introduced 1.11.0-alpha.1; fixed 1.11.17"]}],"null_published_at":"2026-11-03T17:49:21.361Z","source_updated_at":"2026-03-09T16:01:31.134Z","source_disclosed_at":"2024-07-17T14:32:18.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"Source facts changed; compare the preserved prior revision.","null_first_observed_at":"2026-10-31T21:41:49.678Z"},{"id":"NVI-00005180","kind":"vulnerability","title":"Sylius has a security vulnerability via adjustments API endpoint","revision":2,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-55rf-8q29-4g43","CVE-2024-40633"],"plain_summary":"OSV carries this publisher advisory for sylius/sylius, sylius/sylius, 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 1.12.19 for sylius/sylius. Confirm the publisher’s latest guidance.","source_ids":["sr-85d4062b4bb64cbae3093a74e97f9288"],"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 1.13.4 for sylius/sylius. Confirm the publisher’s latest guidance.","source_ids":["sr-85d4062b4bb64cbae3093a74e97f9288"],"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 1.9.12 for sylius/sylius. Confirm the publisher’s latest guidance.","source_ids":["sr-85d4062b4bb64cbae3093a74e97f9288"],"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 1.10.16 for sylius/sylius. Confirm the publisher’s latest guidance.","source_ids":["sr-85d4062b4bb64cbae3093a74e97f9288"],"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 1.11.17 for sylius/sylius. Confirm the publisher’s latest guidance.","source_ids":["sr-85d4062b4bb64cbae3093a74e97f9288"],"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-56b49d39726116356cf7adc9bc5eef29"],"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.380%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.32022. Missing scores are unknown.","source_id":"sr-56b49d39726116356cf7adc9bc5eef29"}],"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-85d4062b4bb64cbae3093a74e97f9288","url":"https://github.com/advisories/GHSA-55rf-8q29-4g43","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-55rf-8q29-4g43","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:41:49.678Z"},{"id":"sr-56b49d39726116356cf7adc9bc5eef29","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-2024-40633","publisher":"FIRST EPSS","observed_at":"2026-10-31T22:06:15.368Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-85d4062b4bb64cbae3093a74e97f9288"],"technology":"sylius/sylius","known_exclusions":[],"conditions_summary":"### Impact\nA 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.\n\n### Patches\nThe issue is fixed in versions: 1.9.12, 1.10.16, 1.11.17, 1.12.19, 1.13.4 and above.\nThe `/api/v2/shop/adjustments/{id}` will always return `404` status.\n\n### Workarounds\n\nUsing YAML configuration:\n\nCreate `config/api_platform/Adjustment.yaml` file:\n\n```yaml\n# config/api_platform/Adjustment.yaml\n\n'%sylius.model.adjustment.class%':\n    itemOperations:\n        shop_get:\n            controller: ApiPlatform\\Core\\Action\\NotFoundAction\n            read: false\n            output: false\n```\n\nOr using XML configuration:\n\n> Note: This is the only way of disabling the vulnerable endpoint for Sylius 1.9, as YAML configuration is not supported in that version.\n\nCopy the original configuration from vendor:\n\n```bash\n# create directory if it doesn't exist\nmkdir -p config/api_platform\n\ncp vendor/sylius/sylius/src/S","public_affected_ranges":["ECOSYSTEM: introduced 1.12.0-alpha.1; fixed 1.12.19"]},{"certainty":"source_listed","source_ids":["sr-85d4062b4bb64cbae3093a74e97f9288"],"technology":"sylius/sylius","known_exclusions":[],"conditions_summary":"### Impact\nA 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.\n\n### Patches\nThe issue is fixed in versions: 1.9.12, 1.10.16, 1.11.17, 1.12.19, 1.13.4 and above.\nThe `/api/v2/shop/adjustments/{id}` will always return `404` status.\n\n### Workarounds\n\nUsing YAML configuration:\n\nCreate `config/api_platform/Adjustment.yaml` file:\n\n```yaml\n# config/api_platform/Adjustment.yaml\n\n'%sylius.model.adjustment.class%':\n    itemOperations:\n        shop_get:\n            controller: ApiPlatform\\Core\\Action\\NotFoundAction\n            read: false\n            output: false\n```\n\nOr using XML configuration:\n\n> Note: This is the only way of disabling the vulnerable endpoint for Sylius 1.9, as YAML configuration is not supported in that version.\n\nCopy the original configuration from vendor:\n\n```bash\n# create directory if it doesn't exist\nmkdir -p config/api_platform\n\ncp vendor/sylius/sylius/src/S","public_affected_ranges":["ECOSYSTEM: introduced 1.13.0-alpha.1; fixed 1.13.4"]},{"certainty":"source_listed","source_ids":["sr-85d4062b4bb64cbae3093a74e97f9288"],"technology":"sylius/sylius","known_exclusions":[],"conditions_summary":"### Impact\nA 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.\n\n### Patches\nThe issue is fixed in versions: 1.9.12, 1.10.16, 1.11.17, 1.12.19, 1.13.4 and above.\nThe `/api/v2/shop/adjustments/{id}` will always return `404` status.\n\n### Workarounds\n\nUsing YAML configuration:\n\nCreate `config/api_platform/Adjustment.yaml` file:\n\n```yaml\n# config/api_platform/Adjustment.yaml\n\n'%sylius.model.adjustment.class%':\n    itemOperations:\n        shop_get:\n            controller: ApiPlatform\\Core\\Action\\NotFoundAction\n            read: false\n            output: false\n```\n\nOr using XML configuration:\n\n> Note: This is the only way of disabling the vulnerable endpoint for Sylius 1.9, as YAML configuration is not supported in that version.\n\nCopy the original configuration from vendor:\n\n```bash\n# create directory if it doesn't exist\nmkdir -p config/api_platform\n\ncp vendor/sylius/sylius/src/S","public_affected_ranges":["ECOSYSTEM: introduced 0; fixed 1.9.12"]},{"certainty":"source_listed","source_ids":["sr-85d4062b4bb64cbae3093a74e97f9288"],"technology":"sylius/sylius","known_exclusions":[],"conditions_summary":"### Impact\nA 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.\n\n### Patches\nThe issue is fixed in versions: 1.9.12, 1.10.16, 1.11.17, 1.12.19, 1.13.4 and above.\nThe `/api/v2/shop/adjustments/{id}` will always return `404` status.\n\n### Workarounds\n\nUsing YAML configuration:\n\nCreate `config/api_platform/Adjustment.yaml` file:\n\n```yaml\n# config/api_platform/Adjustment.yaml\n\n'%sylius.model.adjustment.class%':\n    itemOperations:\n        shop_get:\n            controller: ApiPlatform\\Core\\Action\\NotFoundAction\n            read: false\n            output: false\n```\n\nOr using XML configuration:\n\n> Note: This is the only way of disabling the vulnerable endpoint for Sylius 1.9, as YAML configuration is not supported in that version.\n\nCopy the original configuration from vendor:\n\n```bash\n# create directory if it doesn't exist\nmkdir -p config/api_platform\n\ncp vendor/sylius/sylius/src/S","public_affected_ranges":["ECOSYSTEM: introduced 1.10.0-alpha.1; fixed 1.10.16"]},{"certainty":"source_listed","source_ids":["sr-85d4062b4bb64cbae3093a74e97f9288"],"technology":"sylius/sylius","known_exclusions":[],"conditions_summary":"### Impact\nA 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.\n\n### Patches\nThe issue is fixed in versions: 1.9.12, 1.10.16, 1.11.17, 1.12.19, 1.13.4 and above.\nThe `/api/v2/shop/adjustments/{id}` will always return `404` status.\n\n### Workarounds\n\nUsing YAML configuration:\n\nCreate `config/api_platform/Adjustment.yaml` file:\n\n```yaml\n# config/api_platform/Adjustment.yaml\n\n'%sylius.model.adjustment.class%':\n    itemOperations:\n        shop_get:\n            controller: ApiPlatform\\Core\\Action\\NotFoundAction\n            read: false\n            output: false\n```\n\nOr using XML configuration:\n\n> Note: This is the only way of disabling the vulnerable endpoint for Sylius 1.9, as YAML configuration is not supported in that version.\n\nCopy the original configuration from vendor:\n\n```bash\n# create directory if it doesn't exist\nmkdir -p config/api_platform\n\ncp vendor/sylius/sylius/src/S","public_affected_ranges":["ECOSYSTEM: introduced 1.11.0-alpha.1; fixed 1.11.17"]}],"null_published_at":"2026-11-01T01:45:38.500Z","source_updated_at":"2026-03-09T16:01:31.134Z","source_disclosed_at":"2024-07-17T14:32:18.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:49.678Z"},{"id":"NVI-00005180","kind":"vulnerability","title":"Sylius has a security vulnerability via adjustments API endpoint","revision":1,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-55rf-8q29-4g43","CVE-2024-40633"],"plain_summary":"OSV carries this publisher advisory for sylius/sylius, sylius/sylius, 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 1.12.19 for sylius/sylius. Confirm the publisher’s latest guidance.","source_ids":["sr-85d4062b4bb64cbae3093a74e97f9288"],"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 1.13.4 for sylius/sylius. Confirm the publisher’s latest guidance.","source_ids":["sr-85d4062b4bb64cbae3093a74e97f9288"],"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 1.9.12 for sylius/sylius. Confirm the publisher’s latest guidance.","source_ids":["sr-85d4062b4bb64cbae3093a74e97f9288"],"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 1.10.16 for sylius/sylius. Confirm the publisher’s latest guidance.","source_ids":["sr-85d4062b4bb64cbae3093a74e97f9288"],"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 1.11.17 for sylius/sylius. Confirm the publisher’s latest guidance.","source_ids":["sr-85d4062b4bb64cbae3093a74e97f9288"],"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-85d4062b4bb64cbae3093a74e97f9288","url":"https://github.com/advisories/GHSA-55rf-8q29-4g43","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-55rf-8q29-4g43","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:41:49.678Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-85d4062b4bb64cbae3093a74e97f9288"],"technology":"sylius/sylius","known_exclusions":[],"conditions_summary":"### Impact\nA 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.\n\n### Patches\nThe issue is fixed in versions: 1.9.12, 1.10.16, 1.11.17, 1.12.19, 1.13.4 and above.\nThe `/api/v2/shop/adjustments/{id}` will always return `404` status.\n\n### Workarounds\n\nUsing YAML configuration:\n\nCreate `config/api_platform/Adjustment.yaml` file:\n\n```yaml\n# config/api_platform/Adjustment.yaml\n\n'%sylius.model.adjustment.class%':\n    itemOperations:\n        shop_get:\n            controller: ApiPlatform\\Core\\Action\\NotFoundAction\n            read: false\n            output: false\n```\n\nOr using XML configuration:\n\n> Note: This is the only way of disabling the vulnerable endpoint for Sylius 1.9, as YAML configuration is not supported in that version.\n\nCopy the original configuration from vendor:\n\n```bash\n# create directory if it doesn't exist\nmkdir -p config/api_platform\n\ncp vendor/sylius/sylius/src/S","public_affected_ranges":["ECOSYSTEM: introduced 1.12.0-alpha.1; fixed 1.12.19"]},{"certainty":"source_listed","source_ids":["sr-85d4062b4bb64cbae3093a74e97f9288"],"technology":"sylius/sylius","known_exclusions":[],"conditions_summary":"### Impact\nA 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.\n\n### Patches\nThe issue is fixed in versions: 1.9.12, 1.10.16, 1.11.17, 1.12.19, 1.13.4 and above.\nThe `/api/v2/shop/adjustments/{id}` will always return `404` status.\n\n### Workarounds\n\nUsing YAML configuration:\n\nCreate `config/api_platform/Adjustment.yaml` file:\n\n```yaml\n# config/api_platform/Adjustment.yaml\n\n'%sylius.model.adjustment.class%':\n    itemOperations:\n        shop_get:\n            controller: ApiPlatform\\Core\\Action\\NotFoundAction\n            read: false\n            output: false\n```\n\nOr using XML configuration:\n\n> Note: This is the only way of disabling the vulnerable endpoint for Sylius 1.9, as YAML configuration is not supported in that version.\n\nCopy the original configuration from vendor:\n\n```bash\n# create directory if it doesn't exist\nmkdir -p config/api_platform\n\ncp vendor/sylius/sylius/src/S","public_affected_ranges":["ECOSYSTEM: introduced 1.13.0-alpha.1; fixed 1.13.4"]},{"certainty":"source_listed","source_ids":["sr-85d4062b4bb64cbae3093a74e97f9288"],"technology":"sylius/sylius","known_exclusions":[],"conditions_summary":"### Impact\nA 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.\n\n### Patches\nThe issue is fixed in versions: 1.9.12, 1.10.16, 1.11.17, 1.12.19, 1.13.4 and above.\nThe `/api/v2/shop/adjustments/{id}` will always return `404` status.\n\n### Workarounds\n\nUsing YAML configuration:\n\nCreate `config/api_platform/Adjustment.yaml` file:\n\n```yaml\n# config/api_platform/Adjustment.yaml\n\n'%sylius.model.adjustment.class%':\n    itemOperations:\n        shop_get:\n            controller: ApiPlatform\\Core\\Action\\NotFoundAction\n            read: false\n            output: false\n```\n\nOr using XML configuration:\n\n> Note: This is the only way of disabling the vulnerable endpoint for Sylius 1.9, as YAML configuration is not supported in that version.\n\nCopy the original configuration from vendor:\n\n```bash\n# create directory if it doesn't exist\nmkdir -p config/api_platform\n\ncp vendor/sylius/sylius/src/S","public_affected_ranges":["ECOSYSTEM: introduced 0; fixed 1.9.12"]},{"certainty":"source_listed","source_ids":["sr-85d4062b4bb64cbae3093a74e97f9288"],"technology":"sylius/sylius","known_exclusions":[],"conditions_summary":"### Impact\nA 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.\n\n### Patches\nThe issue is fixed in versions: 1.9.12, 1.10.16, 1.11.17, 1.12.19, 1.13.4 and above.\nThe `/api/v2/shop/adjustments/{id}` will always return `404` status.\n\n### Workarounds\n\nUsing YAML configuration:\n\nCreate `config/api_platform/Adjustment.yaml` file:\n\n```yaml\n# config/api_platform/Adjustment.yaml\n\n'%sylius.model.adjustment.class%':\n    itemOperations:\n        shop_get:\n            controller: ApiPlatform\\Core\\Action\\NotFoundAction\n            read: false\n            output: false\n```\n\nOr using XML configuration:\n\n> Note: This is the only way of disabling the vulnerable endpoint for Sylius 1.9, as YAML configuration is not supported in that version.\n\nCopy the original configuration from vendor:\n\n```bash\n# create directory if it doesn't exist\nmkdir -p config/api_platform\n\ncp vendor/sylius/sylius/src/S","public_affected_ranges":["ECOSYSTEM: introduced 1.10.0-alpha.1; fixed 1.10.16"]},{"certainty":"source_listed","source_ids":["sr-85d4062b4bb64cbae3093a74e97f9288"],"technology":"sylius/sylius","known_exclusions":[],"conditions_summary":"### Impact\nA 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.\n\n### Patches\nThe issue is fixed in versions: 1.9.12, 1.10.16, 1.11.17, 1.12.19, 1.13.4 and above.\nThe `/api/v2/shop/adjustments/{id}` will always return `404` status.\n\n### Workarounds\n\nUsing YAML configuration:\n\nCreate `config/api_platform/Adjustment.yaml` file:\n\n```yaml\n# config/api_platform/Adjustment.yaml\n\n'%sylius.model.adjustment.class%':\n    itemOperations:\n        shop_get:\n            controller: ApiPlatform\\Core\\Action\\NotFoundAction\n            read: false\n            output: false\n```\n\nOr using XML configuration:\n\n> Note: This is the only way of disabling the vulnerable endpoint for Sylius 1.9, as YAML configuration is not supported in that version.\n\nCopy the original configuration from vendor:\n\n```bash\n# create directory if it doesn't exist\nmkdir -p config/api_platform\n\ncp vendor/sylius/sylius/src/S","public_affected_ranges":["ECOSYSTEM: introduced 1.11.0-alpha.1; fixed 1.11.17"]}],"null_published_at":"2026-10-31T22:13:01.453Z","source_updated_at":"2026-03-09T16:01:31.134Z","source_disclosed_at":"2024-07-17T14:32:18.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:49.678Z"}],"next_cursor":null,"snapshot_revision":"42594"}