{"items":[{"id":"NVI-00006752","kind":"vulnerability","title":"Shopware: Unauthorized Payment Trigger for Foreign Orders via /store-api/handle-payment","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-9v5m-39wh-5chq","CVE-2026-48016"],"plain_summary":"OSV carries this publisher advisory for shopware/platform, shopware/platform, shopware/core, shopware/core. 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 6.7.10.1 for shopware/platform. Confirm the publisher’s latest guidance.","source_ids":["sr-c16bdb74a09bc8d709923770a0f8353e"],"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 6.6.10.18 for shopware/platform. Confirm the publisher’s latest guidance.","source_ids":["sr-c16bdb74a09bc8d709923770a0f8353e"],"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 6.7.10.1 for shopware/core. Confirm the publisher’s latest guidance.","source_ids":["sr-c16bdb74a09bc8d709923770a0f8353e"],"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 6.6.10.18 for shopware/core. Confirm the publisher’s latest guidance.","source_ids":["sr-c16bdb74a09bc8d709923770a0f8353e"],"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-0afe5d481008d8437f9c01d743b73c41"],"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-07-20T20:16:43.937Z","value":"4.3 MEDIUM (3.1)","meaning":"security-advisories@github.com severity; no combined Null risk score.","source_id":"sr-49766b2eae47ddc56dec07fe80a77a7c"},{"kind":"EPSS","as_of":"2026-11-05T12:03:04.000Z","value":"0.414%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.35867. Missing scores are unknown.","source_id":"sr-0afe5d481008d8437f9c01d743b73c41"}],"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-c16bdb74a09bc8d709923770a0f8353e","url":"https://github.com/advisories/GHSA-9v5m-39wh-5chq","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-9v5m-39wh-5chq","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:42:10.690Z"},{"id":"sr-49766b2eae47ddc56dec07fe80a77a7c","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-48016","basis":"official_catalog","notes":"This product uses data from the NVD API but is not endorsed or certified by the NVD.","title":"CVE-2026-48016","publisher":"NIST National Vulnerability Database","observed_at":"2026-11-01T07:24:22.913Z"},{"id":"sr-0afe5d481008d8437f9c01d743b73c41","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-48016","publisher":"FIRST EPSS","observed_at":"2026-11-06T00:24:57.659Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-c16bdb74a09bc8d709923770a0f8353e"],"technology":"shopware/platform","known_exclusions":[],"conditions_summary":"## Summary\n\nThe Shopware Store API endpoint `/store-api/handle-payment` contains an object-level authorization flaw that allows a low-privileged external user with a normal customer or guest context to trigger the payment flow for another user’s order by supplying a foreign `orderId`. The affected functionality is the Store API payment initiation and retry flow. The root cause is that the endpoint forwards the user-controlled `orderId` into the payment processing logic without verifying that the caller owns the referenced order or has passed the required guest-order authentication. As a result, payment attempts for foreign orders are accepted by the server, which can compromise the integrity of order and payment workflows.\n\n## Description\n\nShopware exposes `/store-api/handle-payment` to initiate or retry the payment flow for an already created order. Under the normal order access model, customers should only be able to view or act on their own orders, and guest users should only be able to access guest orders after completing additional verification such as `deepLinkCode`, email address, and postal code. The Store API `/store-api/order` route follows this model: authenticated custo","public_affected_ranges":["ECOSYSTEM: introduced 6.7.0.0; fixed 6.7.10.1"]},{"certainty":"source_listed","source_ids":["sr-c16bdb74a09bc8d709923770a0f8353e"],"technology":"shopware/platform","known_exclusions":[],"conditions_summary":"## Summary\n\nThe Shopware Store API endpoint `/store-api/handle-payment` contains an object-level authorization flaw that allows a low-privileged external user with a normal customer or guest context to trigger the payment flow for another user’s order by supplying a foreign `orderId`. The affected functionality is the Store API payment initiation and retry flow. The root cause is that the endpoint forwards the user-controlled `orderId` into the payment processing logic without verifying that the caller owns the referenced order or has passed the required guest-order authentication. As a result, payment attempts for foreign orders are accepted by the server, which can compromise the integrity of order and payment workflows.\n\n## Description\n\nShopware exposes `/store-api/handle-payment` to initiate or retry the payment flow for an already created order. Under the normal order access model, customers should only be able to view or act on their own orders, and guest users should only be able to access guest orders after completing additional verification such as `deepLinkCode`, email address, and postal code. The Store API `/store-api/order` route follows this model: authenticated custo","public_affected_ranges":["ECOSYSTEM: introduced 0; fixed 6.6.10.18"]},{"certainty":"source_listed","source_ids":["sr-c16bdb74a09bc8d709923770a0f8353e"],"technology":"shopware/core","known_exclusions":[],"conditions_summary":"## Summary\n\nThe Shopware Store API endpoint `/store-api/handle-payment` contains an object-level authorization flaw that allows a low-privileged external user with a normal customer or guest context to trigger the payment flow for another user’s order by supplying a foreign `orderId`. The affected functionality is the Store API payment initiation and retry flow. The root cause is that the endpoint forwards the user-controlled `orderId` into the payment processing logic without verifying that the caller owns the referenced order or has passed the required guest-order authentication. As a result, payment attempts for foreign orders are accepted by the server, which can compromise the integrity of order and payment workflows.\n\n## Description\n\nShopware exposes `/store-api/handle-payment` to initiate or retry the payment flow for an already created order. Under the normal order access model, customers should only be able to view or act on their own orders, and guest users should only be able to access guest orders after completing additional verification such as `deepLinkCode`, email address, and postal code. The Store API `/store-api/order` route follows this model: authenticated custo","public_affected_ranges":["ECOSYSTEM: introduced 6.7.0.0; fixed 6.7.10.1"]},{"certainty":"source_listed","source_ids":["sr-c16bdb74a09bc8d709923770a0f8353e"],"technology":"shopware/core","known_exclusions":[],"conditions_summary":"## Summary\n\nThe Shopware Store API endpoint `/store-api/handle-payment` contains an object-level authorization flaw that allows a low-privileged external user with a normal customer or guest context to trigger the payment flow for another user’s order by supplying a foreign `orderId`. The affected functionality is the Store API payment initiation and retry flow. The root cause is that the endpoint forwards the user-controlled `orderId` into the payment processing logic without verifying that the caller owns the referenced order or has passed the required guest-order authentication. As a result, payment attempts for foreign orders are accepted by the server, which can compromise the integrity of order and payment workflows.\n\n## Description\n\nShopware exposes `/store-api/handle-payment` to initiate or retry the payment flow for an already created order. Under the normal order access model, customers should only be able to view or act on their own orders, and guest users should only be able to access guest orders after completing additional verification such as `deepLinkCode`, email address, and postal code. The Store API `/store-api/order` route follows this model: authenticated custo","public_affected_ranges":["ECOSYSTEM: introduced 0; fixed 6.6.10.18"]}],"null_published_at":"2026-11-08T15:11:49.420Z","source_updated_at":"2026-09-10T03:51:08.351Z","source_disclosed_at":"2026-06-04T19:33:54.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:10.690Z"},{"id":"NVI-00006752","kind":"vulnerability","title":"Shopware: Unauthorized Payment Trigger for Foreign Orders via /store-api/handle-payment","revision":2,"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-9v5m-39wh-5chq","CVE-2026-48016"],"plain_summary":"OSV carries this publisher advisory for shopware/platform, shopware/platform, shopware/core, shopware/core. 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 6.7.10.1 for shopware/platform. Confirm the publisher’s latest guidance.","source_ids":["sr-c16bdb74a09bc8d709923770a0f8353e"],"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 6.6.10.18 for shopware/platform. Confirm the publisher’s latest guidance.","source_ids":["sr-c16bdb74a09bc8d709923770a0f8353e"],"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 6.7.10.1 for shopware/core. Confirm the publisher’s latest guidance.","source_ids":["sr-c16bdb74a09bc8d709923770a0f8353e"],"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 6.6.10.18 for shopware/core. Confirm the publisher’s latest guidance.","source_ids":["sr-c16bdb74a09bc8d709923770a0f8353e"],"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-49766b2eae47ddc56dec07fe80a77a7c"],"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-07-20T20:16:43.937Z","value":"4.3 MEDIUM (3.1)","meaning":"security-advisories@github.com severity; no combined Null risk score.","source_id":"sr-49766b2eae47ddc56dec07fe80a77a7c"}],"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-c16bdb74a09bc8d709923770a0f8353e","url":"https://github.com/advisories/GHSA-9v5m-39wh-5chq","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-9v5m-39wh-5chq","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:42:10.690Z"},{"id":"sr-49766b2eae47ddc56dec07fe80a77a7c","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-48016","basis":"official_catalog","notes":"This product uses data from the NVD API but is not endorsed or certified by the NVD.","title":"CVE-2026-48016","publisher":"NIST National Vulnerability Database","observed_at":"2026-11-01T07:24:22.913Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-c16bdb74a09bc8d709923770a0f8353e"],"technology":"shopware/platform","known_exclusions":[],"conditions_summary":"## Summary\n\nThe Shopware Store API endpoint `/store-api/handle-payment` contains an object-level authorization flaw that allows a low-privileged external user with a normal customer or guest context to trigger the payment flow for another user’s order by supplying a foreign `orderId`. The affected functionality is the Store API payment initiation and retry flow. The root cause is that the endpoint forwards the user-controlled `orderId` into the payment processing logic without verifying that the caller owns the referenced order or has passed the required guest-order authentication. As a result, payment attempts for foreign orders are accepted by the server, which can compromise the integrity of order and payment workflows.\n\n## Description\n\nShopware exposes `/store-api/handle-payment` to initiate or retry the payment flow for an already created order. Under the normal order access model, customers should only be able to view or act on their own orders, and guest users should only be able to access guest orders after completing additional verification such as `deepLinkCode`, email address, and postal code. The Store API `/store-api/order` route follows this model: authenticated custo","public_affected_ranges":["ECOSYSTEM: introduced 6.7.0.0; fixed 6.7.10.1"]},{"certainty":"source_listed","source_ids":["sr-c16bdb74a09bc8d709923770a0f8353e"],"technology":"shopware/platform","known_exclusions":[],"conditions_summary":"## Summary\n\nThe Shopware Store API endpoint `/store-api/handle-payment` contains an object-level authorization flaw that allows a low-privileged external user with a normal customer or guest context to trigger the payment flow for another user’s order by supplying a foreign `orderId`. The affected functionality is the Store API payment initiation and retry flow. The root cause is that the endpoint forwards the user-controlled `orderId` into the payment processing logic without verifying that the caller owns the referenced order or has passed the required guest-order authentication. As a result, payment attempts for foreign orders are accepted by the server, which can compromise the integrity of order and payment workflows.\n\n## Description\n\nShopware exposes `/store-api/handle-payment` to initiate or retry the payment flow for an already created order. Under the normal order access model, customers should only be able to view or act on their own orders, and guest users should only be able to access guest orders after completing additional verification such as `deepLinkCode`, email address, and postal code. The Store API `/store-api/order` route follows this model: authenticated custo","public_affected_ranges":["ECOSYSTEM: introduced 0; fixed 6.6.10.18"]},{"certainty":"source_listed","source_ids":["sr-c16bdb74a09bc8d709923770a0f8353e"],"technology":"shopware/core","known_exclusions":[],"conditions_summary":"## Summary\n\nThe Shopware Store API endpoint `/store-api/handle-payment` contains an object-level authorization flaw that allows a low-privileged external user with a normal customer or guest context to trigger the payment flow for another user’s order by supplying a foreign `orderId`. The affected functionality is the Store API payment initiation and retry flow. The root cause is that the endpoint forwards the user-controlled `orderId` into the payment processing logic without verifying that the caller owns the referenced order or has passed the required guest-order authentication. As a result, payment attempts for foreign orders are accepted by the server, which can compromise the integrity of order and payment workflows.\n\n## Description\n\nShopware exposes `/store-api/handle-payment` to initiate or retry the payment flow for an already created order. Under the normal order access model, customers should only be able to view or act on their own orders, and guest users should only be able to access guest orders after completing additional verification such as `deepLinkCode`, email address, and postal code. The Store API `/store-api/order` route follows this model: authenticated custo","public_affected_ranges":["ECOSYSTEM: introduced 6.7.0.0; fixed 6.7.10.1"]},{"certainty":"source_listed","source_ids":["sr-c16bdb74a09bc8d709923770a0f8353e"],"technology":"shopware/core","known_exclusions":[],"conditions_summary":"## Summary\n\nThe Shopware Store API endpoint `/store-api/handle-payment` contains an object-level authorization flaw that allows a low-privileged external user with a normal customer or guest context to trigger the payment flow for another user’s order by supplying a foreign `orderId`. The affected functionality is the Store API payment initiation and retry flow. The root cause is that the endpoint forwards the user-controlled `orderId` into the payment processing logic without verifying that the caller owns the referenced order or has passed the required guest-order authentication. As a result, payment attempts for foreign orders are accepted by the server, which can compromise the integrity of order and payment workflows.\n\n## Description\n\nShopware exposes `/store-api/handle-payment` to initiate or retry the payment flow for an already created order. Under the normal order access model, customers should only be able to view or act on their own orders, and guest users should only be able to access guest orders after completing additional verification such as `deepLinkCode`, email address, and postal code. The Store API `/store-api/order` route follows this model: authenticated custo","public_affected_ranges":["ECOSYSTEM: introduced 0; fixed 6.6.10.18"]}],"null_published_at":"2026-11-01T14:34:07.646Z","source_updated_at":"2026-09-10T03:51:08.351Z","source_disclosed_at":"2026-06-04T19:33:54.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:42:10.690Z"},{"id":"NVI-00006752","kind":"vulnerability","title":"Shopware: Unauthorized Payment Trigger for Foreign Orders via /store-api/handle-payment","revision":1,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-9v5m-39wh-5chq","CVE-2026-48016"],"plain_summary":"OSV carries this publisher advisory for shopware/platform, shopware/platform, shopware/core, shopware/core. 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 6.7.10.1 for shopware/platform. Confirm the publisher’s latest guidance.","source_ids":["sr-c16bdb74a09bc8d709923770a0f8353e"],"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 6.6.10.18 for shopware/platform. Confirm the publisher’s latest guidance.","source_ids":["sr-c16bdb74a09bc8d709923770a0f8353e"],"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 6.7.10.1 for shopware/core. Confirm the publisher’s latest guidance.","source_ids":["sr-c16bdb74a09bc8d709923770a0f8353e"],"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 6.6.10.18 for shopware/core. Confirm the publisher’s latest guidance.","source_ids":["sr-c16bdb74a09bc8d709923770a0f8353e"],"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-c16bdb74a09bc8d709923770a0f8353e","url":"https://github.com/advisories/GHSA-9v5m-39wh-5chq","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-9v5m-39wh-5chq","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:42:10.690Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-c16bdb74a09bc8d709923770a0f8353e"],"technology":"shopware/platform","known_exclusions":[],"conditions_summary":"## Summary\n\nThe Shopware Store API endpoint `/store-api/handle-payment` contains an object-level authorization flaw that allows a low-privileged external user with a normal customer or guest context to trigger the payment flow for another user’s order by supplying a foreign `orderId`. The affected functionality is the Store API payment initiation and retry flow. The root cause is that the endpoint forwards the user-controlled `orderId` into the payment processing logic without verifying that the caller owns the referenced order or has passed the required guest-order authentication. As a result, payment attempts for foreign orders are accepted by the server, which can compromise the integrity of order and payment workflows.\n\n## Description\n\nShopware exposes `/store-api/handle-payment` to initiate or retry the payment flow for an already created order. Under the normal order access model, customers should only be able to view or act on their own orders, and guest users should only be able to access guest orders after completing additional verification such as `deepLinkCode`, email address, and postal code. The Store API `/store-api/order` route follows this model: authenticated custo","public_affected_ranges":["ECOSYSTEM: introduced 6.7.0.0; fixed 6.7.10.1"]},{"certainty":"source_listed","source_ids":["sr-c16bdb74a09bc8d709923770a0f8353e"],"technology":"shopware/platform","known_exclusions":[],"conditions_summary":"## Summary\n\nThe Shopware Store API endpoint `/store-api/handle-payment` contains an object-level authorization flaw that allows a low-privileged external user with a normal customer or guest context to trigger the payment flow for another user’s order by supplying a foreign `orderId`. The affected functionality is the Store API payment initiation and retry flow. The root cause is that the endpoint forwards the user-controlled `orderId` into the payment processing logic without verifying that the caller owns the referenced order or has passed the required guest-order authentication. As a result, payment attempts for foreign orders are accepted by the server, which can compromise the integrity of order and payment workflows.\n\n## Description\n\nShopware exposes `/store-api/handle-payment` to initiate or retry the payment flow for an already created order. Under the normal order access model, customers should only be able to view or act on their own orders, and guest users should only be able to access guest orders after completing additional verification such as `deepLinkCode`, email address, and postal code. The Store API `/store-api/order` route follows this model: authenticated custo","public_affected_ranges":["ECOSYSTEM: introduced 0; fixed 6.6.10.18"]},{"certainty":"source_listed","source_ids":["sr-c16bdb74a09bc8d709923770a0f8353e"],"technology":"shopware/core","known_exclusions":[],"conditions_summary":"## Summary\n\nThe Shopware Store API endpoint `/store-api/handle-payment` contains an object-level authorization flaw that allows a low-privileged external user with a normal customer or guest context to trigger the payment flow for another user’s order by supplying a foreign `orderId`. The affected functionality is the Store API payment initiation and retry flow. The root cause is that the endpoint forwards the user-controlled `orderId` into the payment processing logic without verifying that the caller owns the referenced order or has passed the required guest-order authentication. As a result, payment attempts for foreign orders are accepted by the server, which can compromise the integrity of order and payment workflows.\n\n## Description\n\nShopware exposes `/store-api/handle-payment` to initiate or retry the payment flow for an already created order. Under the normal order access model, customers should only be able to view or act on their own orders, and guest users should only be able to access guest orders after completing additional verification such as `deepLinkCode`, email address, and postal code. The Store API `/store-api/order` route follows this model: authenticated custo","public_affected_ranges":["ECOSYSTEM: introduced 6.7.0.0; fixed 6.7.10.1"]},{"certainty":"source_listed","source_ids":["sr-c16bdb74a09bc8d709923770a0f8353e"],"technology":"shopware/core","known_exclusions":[],"conditions_summary":"## Summary\n\nThe Shopware Store API endpoint `/store-api/handle-payment` contains an object-level authorization flaw that allows a low-privileged external user with a normal customer or guest context to trigger the payment flow for another user’s order by supplying a foreign `orderId`. The affected functionality is the Store API payment initiation and retry flow. The root cause is that the endpoint forwards the user-controlled `orderId` into the payment processing logic without verifying that the caller owns the referenced order or has passed the required guest-order authentication. As a result, payment attempts for foreign orders are accepted by the server, which can compromise the integrity of order and payment workflows.\n\n## Description\n\nShopware exposes `/store-api/handle-payment` to initiate or retry the payment flow for an already created order. Under the normal order access model, customers should only be able to view or act on their own orders, and guest users should only be able to access guest orders after completing additional verification such as `deepLinkCode`, email address, and postal code. The Store API `/store-api/order` route follows this model: authenticated custo","public_affected_ranges":["ECOSYSTEM: introduced 0; fixed 6.6.10.18"]}],"null_published_at":"2026-10-31T22:13:10.071Z","source_updated_at":"2026-09-10T03:51:08.351Z","source_disclosed_at":"2026-06-04T19:33:54.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:10.690Z"}],"next_cursor":null,"snapshot_revision":"42594"}