How to use this reference
Editorial lesson: check that each payment, refund or fulfillment belongs to an order in the current channel before changing state or contacting a payment gateway. A later database rejection cannot reliably undo an earlier gateway action. Apply the same checks at every entry point; restricting access to an order does not automatically protect changes to its related objects.
Before reading
- Basic authorization, application state machines and database transaction concepts
Context and limits
- The reported setting is multi-channel commerce with channel-scoped order-update permission and suitable payment configuration. The advisory reports controlled refund evidence and potential financial disruption; production losses are not established.
- The advisory lists versions below 3.7.3 as affected and 3.7.3 as patched. Release notes confirm channel enforcement and advise upgrading related packages together.
- michaelbromley published the advisory; squinard1478 and raysabee are credited reporters. No CVE is assigned on the reviewed page.
- The release rendering displays September 2 without a year; no complete patch-release date is asserted. Resource edition and its release date remain null.
Sources
- Cross-channel payment/refund IDOR — money movement across tenants (payment-side sibling of GHSA-frwg)Vendure · reviewed 2026-10-03
- Vendure v3.7.3 releaseVendure · reviewed 2026-10-03
Record reviewed 2026-10-03. Snapshot af2809c308fc. Open the complete JSON contract.