Act nowVulnerabilities

Drupal Commerce Core has an access bypass that attackers are already exploiting: update and audit your orders

Drupal's security team said on 28 Oct 2026 that Commerce Core has a highly critical access bypass (CVE-2026-118539) that is being actively exploited and can hit a shop's money. Fixed in 3.3.13 and 8.x-2.41. Here is what to do.

How urgent

Act now

Who is affected

Online shops that run the Drupal Commerce Core module below 8.x-2.41, or from 3.0.0 up to but not including 3.3.13. Drupal says all module configurations are exploitable and anonymous visitors can trigger it. Not relevant if you do not run Drupal Commerce

What to do

Update Commerce Core to 3.3.13 (3.x) or 8.x-2.41 (older), and then audit your orders for inconsistencies, because exploitation is already happening. Drupal lists no workaround

Published 30 Oct 2026 · Sources last checked 30 Oct 2026No. 25 / 87

What happened

On 28 October 2026 the Drupal Security Team published SA-CONTRIB-2026-254 for Commerce Core, the main module behind online shops built on Drupal. It is rated highly critical (21 out of 25) and has the identifier CVE-2026-118539. The module does not properly protect some routes and entity fields, which allows an access bypass that can cause financial harm to the shop owner. The advisory states that it is being actively exploited in the wild and that exploitExploit A piece of code or a technique that takes advantage of a specific flaw to get something the attacker should not get. Tap again to open the glossary code exists.

Who is affected

  • Shops that run Commerce Core below 8.x-2.41, or from 3.0.0 up to but not including 3.3.13.
  • Drupal rates it as needing no login and no special conditions: a visitor only needs to load a page. It says some non-public data can be read and some data can be changed, and that every module configuration is exploitable.
  • If you do not run Drupal Commerce, this story does not apply to you.

What to do

Steps follow Drupal's advisory.

  1. Update now: Commerce Core 3.3.13 if you are on 3.x, or 8.x-2.41 if you are on an older line.
  2. Audit your orders for inconsistencies, such as odd totals, payment statuses that do not match your payment provider, or orders you cannot explain. Drupal asks sites to do this because exploitation is already happening.
  3. There is no workaround in the advisory, so updating is the only fix.

If you build with AI tools

Our advice, not from Drupal: if an AI assistant wrote or edited part of your shop, check which modules it added and which versions are installed, and make updates for payment and order modules a standing weekly task.

What we could not confirm

Drupal's advisory does not say how many shops were attacked, what exactly the attackers changed, or who they are. We have not seen indicators to search for beyond the instruction to audit orders. Drupal published five other Commerce Core advisories on the same day, with lower ratings; we have not covered them here.

Comments

No account needed. Add a nickname if you like, or leave it empty to comment anonymously. Comments are reviewed before they appear. Links are not allowed.

    We store your comment, your nickname and a scrambled form of your connection that we use only to limit spam. We do not store your IP address or set cookies. Cloudflare Turnstile checks that you are not a bot.

    Sources and verification

    We use primary sources first and say when we rely on a news report. Dates are the day we last checked each source.

    Spotted a mistake? Email [email protected] and we will correct it and note the change.

    Get the free runbooks

    One-page security checklists for founders who build with AI. You get a confirmation email first, then the runbooks.

    Send me the runbooks