Skip to main content
VulnerabilityPublished

CVE-2026-126732: Commerce license · This module enables you to sell licenses that grant access to resources (such as

Affects drupal/commerce_licenseSource GCVE Database

0
Compare

Not known to be exploited : upgrade to 3.1.2 soon.

Data as of 11 Nov 2026, 20:18 UTC

Severity
High

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

Patch
Available – fixed in 3.1.2

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 11 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 11 Nov 2026.

What to do

Upgrade drupal/commerce_license to 3.1.2.

Affected software

ProductAffectedFixed in
Packagist https //packages.drupal.org/8drupal/commerce_licenseAffected
  • <3.1.2
Fixed in
  • 3.1.2

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

AI-suggested

Upgrade to Commerce License module version 3.1.2 or later, where this vulnerability is fixed. Additionally, ensure that JSON:API or REST write permissions to order items are carefully controlled or disabled if not required, as this configuration is necessary for exploitation.

Description

The Drupal Commerce License module allows selling licenses granting access to resources like roles. A vulnerability exists due to insufficient validation of the license referenced by an order item, enabling an attacker to take over another user's license. This issue requires JSON:API or REST to be configured to allow writes to order items, which is not the default configuration. The vulnerability is fixed in version 3.1.2.

References

Community reviews

Loading reviews…