Skip to main content
VulnerabilityPublished

CVE-2026-122071: Commerce escrow · This module enables you to accept payments through Escrow.com with Drupal Commerce

Affects drupal/commerce_escrowSource GCVE Database

0
Compare

Not known to be exploited : upgrade to 1.1.0 soon.

Data as of 4 Nov 2026, 21:16 UTC

Severity
High

Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD

Patch
Available – fixed in 1.1.0

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 4 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 4 Nov 2026.

What to do

Upgrade drupal/commerce_escrow to 1.1.0.

Affected software

ProductAffectedFixed in
Packagist https //packages.drupal.org/8drupal/commerce_escrowAffected
  • <1.1.0
Fixed in
  • 1.1.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade the Drupal Commerce Escrow module to version 1.1.0 or later, where the vulnerability is fixed. Applying this official fix will ensure proper verification of Escrow.com webhook notifications and prevent unauthorized order status manipulation.

Description

The Drupal Commerce Escrow module before version 1.1.0 does not properly verify incoming webhook notifications from Escrow.com. This flaw allows attackers to forge payment and order status updates, potentially marking unpaid orders as paid or completed, or cancelling orders that are in progress.

References

Community reviews

Loading reviews…