Skip to main content
All incident reports
Incident report

Drupal Commerce Core access bypass exploited in the wild

Drupal says attackers are exploiting a highly critical access bypass in its Commerce Core module, tracked as CVE-2026-118539. The flaw is a missing authorisation check that can let unauthenticated users reach routes and entity fields that should be protected, and Drupal has told site owners to patch and audit orders.

· First published

The short version

  • The flaw. Drupal has published an advisory for CVE-2026-118539, a missing authorisation weakness in Commerce Core that can let unauthenticated attackers bypass access controls on certain routes and entity fields. The affected releases are 0.0.0 through 2.41 and 3.0.0 through 3.3.13.
  • Exploitation. Drupal says the flaw is being actively exploited in the wild. It has not said how the bug is exploited, who is behind the activity or how many sites were targeted, and it has not said whether attacks began before patches were available.
  • Exposure. Commerce Core is a community-developed e-commerce module used on more than 42,000 Drupal websites, according to Drupal's statistics. BleepingComputer reports that users include Fortune 500 companies and research universities.
  • Risk. Drupal gave the issue a risk score of 21 out of 25 and says unauthenticated attackers can exploit it regardless of how the module is configured.
  • Advice. Administrators on the 3.x branch should upgrade to Commerce Core 3.3.13; earlier branches have a separate fixed release named in Drupal's advisory. Drupal also advises auditing orders for inconsistencies.

The vulnerability

Drupal's advisory describes a highly critical access bypass in Commerce Core, a contributed module that adds a shopping cart, checkout and API features to Drupal sites. Drupal says the module does not sufficiently protect certain routes and entity fields, creating an access bypass that may financially affect the vendor. Drupal credited researchers Dan Puccetti, Marcus Johansson and Robert Snyder with reporting the flaw.

SecurityWeek reports that Drupal rated the issue 21 out of 25 and that unauthenticated attackers can exploit it however the module is set up. BleepingComputer says the weakness stems from missing authorisation and can be abused by unauthenticated attackers.

Who is exposed

Commerce Core is used on more than 42,000 websites, according to Drupal's statistics cited by SecurityWeek. BleepingComputer says those users include high-profile organisations such as Fortune 500 companies and research universities, and that the module provides a framework for e-commerce sites and shopping apps built on Drupal.

Drupal's security team told administrators on the 3.x branch to upgrade immediately to Commerce Core 3.3.13 and to audit orders for inconsistencies. SecurityWeek reports that Drupal confirmed the attacks but has not said how the bug is exploited, who is responsible, how many sites were targeted or whether the flaw was used as a zero-day.

Wider Drupal security work

The Commerce Core advisory arrived during a period of active Drupal security work. SecurityWeek reports that Drupal published 38 other advisories on 28 October covering 21 contributed projects, with nearly a dozen rated critical and some capable of remote code execution or account takeover.

Drupal also fixed two critical remote code execution bugs on 14 October and warned that exploits might appear within hours or days, according to SecurityWeek. The same report says there have been no public reports of those two flaws being exploited in the wild.

What is not known yet

  • Who is exploiting the flaw and what they are seeking to gain.
  • How many sites have been attacked or affected.
  • Whether the flaw was used as a zero-day before fixed releases were available.
  • Whether any orders, payment records or customer data were altered or taken.
  • Which routes or entity fields attackers are targeting.

What to do

If you run Drupal Commerce Core

  1. Check whether your site uses Commerce Core in an affected release: 0.0.0 to 2.41 or 3.0.0 to 3.3.13.
  2. Upgrade 3.x sites to Commerce Core 3.3.13 and earlier-branch sites to the fixed release named in Drupal's advisory.
  3. Audit store orders for inconsistencies, as Drupal advises.
  4. Apply the update promptly because Drupal says the flaw is being actively exploited.

If you manage Drupal sites for others

  1. Inventory every site you manage for Commerce Core and record its version.
  2. Patch affected sites and track completion across the estate.
  3. Give site owners the fixed-version details from Drupal's advisory so they can confirm their own remediation.

For everyone else

  1. Treat add-on modules as part of your attack surface, not just the core platform.
  2. Subscribe to Drupal security advisories and act on notices that a flaw is being actively exploited.
  3. Set a patch timeline for payment-related software that reflects active exploitation.

Update log

  • First published.

Sources

New incident reports by email

One email a week with the reports published since the last one.

Want us to look at your domain?

Give us one apex domain and we'll send back a written snapshot of what is already visible from outside. No call required.