CVE-2026-122071: Webhook verification bypass in Drupal Commerce Escrow
The Drupal Commerce Escrow module before version 1.1.0 insufficiently verifies incoming Escrow.com webhook notifications. An unauthenticated attacker can submit forged notifications to manipulate payment and order status, marking unpaid orders as paid or completed or cancelling orders that are in progress.
Impact, mitigation & remediation
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Successful exploitation compromises payment and order integrity. Fraudulent status changes can cause financial loss through unpaid orders being treated as paid or completed, while unauthorized cancellation of orders in progress can disrupt business operations.
Remediation
Patch, then assume compromise.
Upgrade to Commerce Escrow 1.1.0 or a later supported version. The 1.0.x release line is no longer supported. After upgrading, register the new webhook URL with Escrow.com; the URL is displayed on the configuration form for each Escrow payment gateway.
Exploits
No public exploits tracked yet. Mallory keeps watching.
References
Frequently asked questions
- Is CVE-2026-122071 exploited in the wild?
- As of Nov 4, 2026, Mallory has no reports of CVE-2026-122071 being exploited in the wild. It is not listed in CISA KEV.
- Is there a public exploit for CVE-2026-122071?
- As of Nov 4, 2026, Mallory has found no public exploit for CVE-2026-122071.
- Is there a patch for CVE-2026-122071?
- Upgrade to Commerce Escrow 1.1.0 or a later supported version. The 1.0.x release line is no longer supported.
Recent activity
1 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.