Drupal’s Security Team says attackers are actively exploiting an access bypass in Commerce Core, the module that provides shopping carts, checkout and commerce APIs. Its October 28 advisory, SA-CONTRIB-2026-254, identifies CVE-2026-118539 and tells site owners to audit their orders for inconsistencies.

Evidence status: exploitation reported by the project’s Security Team. Sergiu Gatlan’s October 30 BleepingComputer report relays that warning. Neither reviewed source supplies a victim count, loss total or public forensic account of particular attacks.

The advisory says the module fails to sufficiently protect certain routes and entity fields, allowing access that may financially harm the merchant. Its risk assessment specifies no authentication requirement and all module configurations as exploitable. This concerns sites using the affected Commerce Core releases, rather than every site running Drupal itself.

The fixed releases are outside the affected ranges

The primary advisory gives the affected range as <2.41 || >=3.0.0 <3.3.13. Its prescribed fixes are:

Commerce Core branch Affected versions First fixed release
Earlier branch Before 2.41 8.x-2.41
3.x From 3.0.0, before 3.3.13 3.3.13

Both 3.3.13 and 8.x-2.41 have official October 28 security-release pages. The boundary versions are fixes, not affected endpoints. BleepingComputer’s introductory “through” wording includes those endpoints, while its action guidance and Drupal’s advisory identify them as the upgrades.

Check the deployed Commerce Core module version, alongside the site’s Drupal version. Updating Drupal core alone does not establish that this contributed module has received its fix. Follow the release guidance for the branch actually in use and verify the repaired module is deployed.

Patching and checking past orders are separate jobs

The Security Team explicitly recommends both installing the update and auditing orders. A repair closes the documented access gap; it cannot establish that earlier transactions were legitimate.

For a merchant responding to the advisory:

  • Install a release containing the fix, following the project’s supported update process.
  • Preserve relevant application, request and transaction records for reviewing activity before the update.
  • Reconcile orders with payment and fulfillment records to investigate unexpected inconsistencies. This is a practical way to carry out the advised audit, not a published indicator that every discrepancy proves exploitation.
  • Keep suspicious transactions under investigation rather than treating a successful upgrade as evidence that no earlier abuse occurred.

The advisory does not identify specific abused routes, field changes, an attack start date or a universal compromise-checking procedure. Its financial-impact warning should not be expanded into an unsupported claim of server takeover or payment-card theft.

Caveat: the exploitation assessment comes from the affected project’s Security Team. The reviewed reporting repeats it without independently measuring the campaign’s reach.