{"items":[{"id":"NVI-00006330","kind":"vulnerability","title":"Craft Commerce has an unauthenticated information disclosure that can leak some customer order data on anonymous payments","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-3vxg-x5f8-f5qf","CVE-2026-32270"],"plain_summary":"OSV carries this publisher advisory for craftcms/commerce, craftcms/commerce. 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 5.6.0 for craftcms/commerce. Confirm the publisher’s latest guidance.","source_ids":["sr-b08fff80784cfe9c382a9b0b89cc2c14"],"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 4.11.0 for craftcms/commerce. Confirm the publisher’s latest guidance.","source_ids":["sr-b08fff80784cfe9c382a9b0b89cc2c14"],"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-0b62887cda871c72bd7ede6016008c2e"],"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-10-26T22:10:00.163Z","value":"1.7 LOW (4.0)","meaning":"security-advisories@github.com severity; no combined Null risk score.","source_id":"sr-9d91340789ae29c482ebabb6504442dd"},{"kind":"EPSS","as_of":"2026-11-02T12:00:30.000Z","value":"0.295%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.22137. Missing scores are unknown.","source_id":"sr-0b62887cda871c72bd7ede6016008c2e"}],"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-b08fff80784cfe9c382a9b0b89cc2c14","url":"https://github.com/advisories/GHSA-3vxg-x5f8-f5qf","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-3vxg-x5f8-f5qf","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:41:49.660Z"},{"id":"sr-9d91340789ae29c482ebabb6504442dd","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-32270","basis":"official_catalog","notes":"This product uses data from the NVD API but is not endorsed or certified by the NVD.","title":"CVE-2026-32270","publisher":"NIST National Vulnerability Database","observed_at":"2026-11-01T07:22:50.140Z"},{"id":"sr-0b62887cda871c72bd7ede6016008c2e","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-32270","publisher":"FIRST EPSS","observed_at":"2026-11-02T20:15:58.850Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-b08fff80784cfe9c382a9b0b89cc2c14"],"technology":"craftcms/commerce","known_exclusions":[],"conditions_summary":"### Summary\n\n`PaymentsController::actionPay` discloses some order data to unauthenticated users when an order number is provided and the email check fails during an anonymous payment.\n\nThe JSON error response includes the serialized order object (`order`), which contains some sensitive fields such as customer email, shipping address, and billing address.\n\n### Details\n\nI manually audited frontend payment flows and found that `actionPay()` retrieves orders by number before authorization is fully enforced.\n\nCode path:\n\n1. Load order by `number`.\n2. Evaluate whether payment is authorized for completed orders (`number + matching email`).\n3. If unauthorized, return failure.\n4. Failure response still includes `cartArray($order)`, which serializes sensitive order data.\n\nWhy is this a vulnerability?\n\n- Authorization logic says the requester is not allowed to pay for a completed order without an email.\n- But the response still returns the same completed order’s contents.\n\n### Impact\n\nType: Information Disclosure / Broken Access Control\n\nWho is impacted:\n\n- Any Commerce deployment where completed order numbers can be obtained or leaked.","public_affected_ranges":["ECOSYSTEM: introduced 5.0.0; fixed 5.6.0"]},{"certainty":"source_listed","source_ids":["sr-b08fff80784cfe9c382a9b0b89cc2c14"],"technology":"craftcms/commerce","known_exclusions":[],"conditions_summary":"### Summary\n\n`PaymentsController::actionPay` discloses some order data to unauthenticated users when an order number is provided and the email check fails during an anonymous payment.\n\nThe JSON error response includes the serialized order object (`order`), which contains some sensitive fields such as customer email, shipping address, and billing address.\n\n### Details\n\nI manually audited frontend payment flows and found that `actionPay()` retrieves orders by number before authorization is fully enforced.\n\nCode path:\n\n1. Load order by `number`.\n2. Evaluate whether payment is authorized for completed orders (`number + matching email`).\n3. If unauthorized, return failure.\n4. Failure response still includes `cartArray($order)`, which serializes sensitive order data.\n\nWhy is this a vulnerability?\n\n- Authorization logic says the requester is not allowed to pay for a completed order without an email.\n- But the response still returns the same completed order’s contents.\n\n### Impact\n\nType: Information Disclosure / Broken Access Control\n\nWho is impacted:\n\n- Any Commerce deployment where completed order numbers can be obtained or leaked.","public_affected_ranges":["ECOSYSTEM: introduced 4.0.0; fixed 4.11.0"]}],"null_published_at":"2026-11-06T15:18:11.513Z","source_updated_at":"2026-04-14T01:39:12.407Z","source_disclosed_at":"2026-04-14T01:01:17.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.660Z"},{"id":"NVI-00006330","kind":"vulnerability","title":"Craft Commerce has an unauthenticated information disclosure that can leak some customer order data on anonymous payments","revision":2,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-3vxg-x5f8-f5qf","CVE-2026-32270"],"plain_summary":"OSV carries this publisher advisory for craftcms/commerce, craftcms/commerce. 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 5.6.0 for craftcms/commerce. Confirm the publisher’s latest guidance.","source_ids":["sr-b08fff80784cfe9c382a9b0b89cc2c14"],"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 4.11.0 for craftcms/commerce. Confirm the publisher’s latest guidance.","source_ids":["sr-b08fff80784cfe9c382a9b0b89cc2c14"],"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-0b62887cda871c72bd7ede6016008c2e"],"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.295%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.22137. Missing scores are unknown.","source_id":"sr-0b62887cda871c72bd7ede6016008c2e"}],"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-b08fff80784cfe9c382a9b0b89cc2c14","url":"https://github.com/advisories/GHSA-3vxg-x5f8-f5qf","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-3vxg-x5f8-f5qf","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:41:49.660Z"},{"id":"sr-0b62887cda871c72bd7ede6016008c2e","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-32270","publisher":"FIRST EPSS","observed_at":"2026-11-02T20:15:58.850Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-b08fff80784cfe9c382a9b0b89cc2c14"],"technology":"craftcms/commerce","known_exclusions":[],"conditions_summary":"### Summary\n\n`PaymentsController::actionPay` discloses some order data to unauthenticated users when an order number is provided and the email check fails during an anonymous payment.\n\nThe JSON error response includes the serialized order object (`order`), which contains some sensitive fields such as customer email, shipping address, and billing address.\n\n### Details\n\nI manually audited frontend payment flows and found that `actionPay()` retrieves orders by number before authorization is fully enforced.\n\nCode path:\n\n1. Load order by `number`.\n2. Evaluate whether payment is authorized for completed orders (`number + matching email`).\n3. If unauthorized, return failure.\n4. Failure response still includes `cartArray($order)`, which serializes sensitive order data.\n\nWhy is this a vulnerability?\n\n- Authorization logic says the requester is not allowed to pay for a completed order without an email.\n- But the response still returns the same completed order’s contents.\n\n### Impact\n\nType: Information Disclosure / Broken Access Control\n\nWho is impacted:\n\n- Any Commerce deployment where completed order numbers can be obtained or leaked.","public_affected_ranges":["ECOSYSTEM: introduced 5.0.0; fixed 5.6.0"]},{"certainty":"source_listed","source_ids":["sr-b08fff80784cfe9c382a9b0b89cc2c14"],"technology":"craftcms/commerce","known_exclusions":[],"conditions_summary":"### Summary\n\n`PaymentsController::actionPay` discloses some order data to unauthenticated users when an order number is provided and the email check fails during an anonymous payment.\n\nThe JSON error response includes the serialized order object (`order`), which contains some sensitive fields such as customer email, shipping address, and billing address.\n\n### Details\n\nI manually audited frontend payment flows and found that `actionPay()` retrieves orders by number before authorization is fully enforced.\n\nCode path:\n\n1. Load order by `number`.\n2. Evaluate whether payment is authorized for completed orders (`number + matching email`).\n3. If unauthorized, return failure.\n4. Failure response still includes `cartArray($order)`, which serializes sensitive order data.\n\nWhy is this a vulnerability?\n\n- Authorization logic says the requester is not allowed to pay for a completed order without an email.\n- But the response still returns the same completed order’s contents.\n\n### Impact\n\nType: Information Disclosure / Broken Access Control\n\nWho is impacted:\n\n- Any Commerce deployment where completed order numbers can be obtained or leaked.","public_affected_ranges":["ECOSYSTEM: introduced 4.0.0; fixed 4.11.0"]}],"null_published_at":"2026-11-04T10:04:41.584Z","source_updated_at":"2026-04-14T01:39:12.407Z","source_disclosed_at":"2026-04-14T01:01:17.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.660Z"},{"id":"NVI-00006330","kind":"vulnerability","title":"Craft Commerce has an unauthenticated information disclosure that can leak some customer order data on anonymous payments","revision":1,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-3vxg-x5f8-f5qf","CVE-2026-32270"],"plain_summary":"OSV carries this publisher advisory for craftcms/commerce, craftcms/commerce. 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 5.6.0 for craftcms/commerce. Confirm the publisher’s latest guidance.","source_ids":["sr-b08fff80784cfe9c382a9b0b89cc2c14"],"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 4.11.0 for craftcms/commerce. Confirm the publisher’s latest guidance.","source_ids":["sr-b08fff80784cfe9c382a9b0b89cc2c14"],"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-b08fff80784cfe9c382a9b0b89cc2c14","url":"https://github.com/advisories/GHSA-3vxg-x5f8-f5qf","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-3vxg-x5f8-f5qf","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:41:49.660Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-b08fff80784cfe9c382a9b0b89cc2c14"],"technology":"craftcms/commerce","known_exclusions":[],"conditions_summary":"### Summary\n\n`PaymentsController::actionPay` discloses some order data to unauthenticated users when an order number is provided and the email check fails during an anonymous payment.\n\nThe JSON error response includes the serialized order object (`order`), which contains some sensitive fields such as customer email, shipping address, and billing address.\n\n### Details\n\nI manually audited frontend payment flows and found that `actionPay()` retrieves orders by number before authorization is fully enforced.\n\nCode path:\n\n1. Load order by `number`.\n2. Evaluate whether payment is authorized for completed orders (`number + matching email`).\n3. If unauthorized, return failure.\n4. Failure response still includes `cartArray($order)`, which serializes sensitive order data.\n\nWhy is this a vulnerability?\n\n- Authorization logic says the requester is not allowed to pay for a completed order without an email.\n- But the response still returns the same completed order’s contents.\n\n### Impact\n\nType: Information Disclosure / Broken Access Control\n\nWho is impacted:\n\n- Any Commerce deployment where completed order numbers can be obtained or leaked.","public_affected_ranges":["ECOSYSTEM: introduced 5.0.0; fixed 5.6.0"]},{"certainty":"source_listed","source_ids":["sr-b08fff80784cfe9c382a9b0b89cc2c14"],"technology":"craftcms/commerce","known_exclusions":[],"conditions_summary":"### Summary\n\n`PaymentsController::actionPay` discloses some order data to unauthenticated users when an order number is provided and the email check fails during an anonymous payment.\n\nThe JSON error response includes the serialized order object (`order`), which contains some sensitive fields such as customer email, shipping address, and billing address.\n\n### Details\n\nI manually audited frontend payment flows and found that `actionPay()` retrieves orders by number before authorization is fully enforced.\n\nCode path:\n\n1. Load order by `number`.\n2. Evaluate whether payment is authorized for completed orders (`number + matching email`).\n3. If unauthorized, return failure.\n4. Failure response still includes `cartArray($order)`, which serializes sensitive order data.\n\nWhy is this a vulnerability?\n\n- Authorization logic says the requester is not allowed to pay for a completed order without an email.\n- But the response still returns the same completed order’s contents.\n\n### Impact\n\nType: Information Disclosure / Broken Access Control\n\nWho is impacted:\n\n- Any Commerce deployment where completed order numbers can be obtained or leaked.","public_affected_ranges":["ECOSYSTEM: introduced 4.0.0; fixed 4.11.0"]}],"null_published_at":"2026-10-31T22:13:10.051Z","source_updated_at":"2026-04-14T01:39:12.407Z","source_disclosed_at":"2026-04-14T01:01:17.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.660Z"}],"next_cursor":null,"snapshot_revision":"42594"}