
Hackers are placing fraudulent orders on Drupal Commerce stores right now. Two merchants flagged suspicious activity before Drupal even published the advisory — meaning attacks were live before defenders knew a patch existed. The flaw, CVE-2026-118539, is a missing authorization bug in Commerce Core that lets unauthenticated attackers bypass the checkout flow entirely, place orders at manipulated prices, and leave stores with “paid” orders that were never actually paid. Drupal rates it 21 out of 25 — Highly Critical.
What the Flaw Does
Commerce Core does not adequately protect certain routes and entity fields. An unauthenticated attacker can request those routes directly, skipping the checkout steps that validate pricing, coupons, and payment state. Drupal has not disclosed which routes are affected — a deliberate choice to slow down further exploitation — but the Centarro team (Commerce Core maintainers) published enough forensic detail to understand the attack pattern.
The key insight: Drupal Commerce separates checkout completion from payment receipt. Checkout marks an order as complete when it reaches the final step. Payment is confirmed separately. The exploit skips the checkout steps entirely, placing an order directly and leaving the checkout_step field unchanged. It can also set the total_paid field on an order without completing any actual payments. The result: an order that looks complete and paid, that was never paid.
More than 42,000 sites run Commerce Core. Fortune 500 companies, research universities, and government sites are in that pool. Headless and API-driven Drupal storefronts are affected alongside traditional installations.
Check If You Were Already Hit
The patch is necessary, but it does not undo damage that already happened. Before you upgrade, audit your orders. Centarro published SQL-based audit guidance after receiving reports from compromised merchants.
Two reliable indicators of exploitation:
- Unchanged
checkout_step: The exploit places orders directly without progressing through checkout. Legitimate orders advance through each checkout step before completion. An order that skipped all steps is a red flag. - Inflated
total_paid: Drupal Commerce calculatestotal_paidby summing completed payment transactions. If an order’stotal_paidis higher than what the payment system recorded, an attacker set that field manually.
Check /admin/commerce/orders for recent orders with unusual prices, inconsistent payment records, or orders that jumped straight to complete status. Do not rely solely on low prices as a signal — merchants reported both $0.01 orders and normal-price manipulated orders. Read the full Drupal Security Advisory SA-CONTRIB-2026-254 for complete details.
How to Patch
There are two supported branches. Use the right one for your installation:
3.x branch (current): Upgrade to Commerce Core 3.3.13
composer require drupal/commerce:^3.3.13
drush updatedb
drush cache:rebuild
Legacy 8.x branch: Upgrade to Commerce Core 8.x-2.41
composer require drupal/commerce:~8.2.41
drush updatedb
drush cache:rebuild
If you are unsure which version you are running:
drush pm:list | grep commerce
Patched versions were released on October 28, 2026. Full patch notes are in the official advisory.
Why This Attack Pattern Is Harder to Detect Than Card Fraud
Traditional payment fraud detection focuses on card anomalies — mismatched billing addresses, velocity checks, high-risk BINs. This attack never touches the payment layer. It manipulates the order state at the application layer before payment is processed. Standard fraud tooling will not catch it.
This is the new ecommerce attack pattern: bypass the checkout flow, not the payment processor. October 2026 has already produced a string of pre-authentication exploits — GitLab CVE-2026-110264 (CVSS 10.0), PHP2Shell, and now this. The common thread: authorization checks are complex, often an afterthought, and consistently where attackers find their footholds. CWE-862 (Missing Authorization) sits in the OWASP Broken Access Control category for a reason.
If you run Drupal Commerce, treat this as a zero-day that has been live since before the patch existed. Upgrade immediately, audit your orders, and verify payment records before fulfilling anything you cannot reconcile.

