CVE Tools

CVE-2026-118539

Commerce Core - Highly critical - Access bypass - SA-CONTRIB-2026-254

No known exploitation. EPSS puts it in the 13th percentile. Fixed versions are out.

Published Updated Sources: CVE.org, NVD

What to do

Find your product and version, then upgrade to the build on the right.

  • Drupal Commerce CoreAffected: ≥ 0.0.0, < 2.41Upgrade to: 2.41Affected: ≥ 3.0.0, < 3.3.13Upgrade to: 3.3.13Stated by: CVE record

Versions as the sources state them. Full version matrix after sign-in

Steps

Written by AI from the record
  1. Check which version of Commerce Core your Drupal site is running (ask your developer or site administrator if unsure).
  2. If you're on the 2.x branch, upgrade to Commerce Core 2.41 or later.
  3. If you're on the 3.x branch, upgrade to Commerce Core 3.3.13 or later.
  4. Confirm with whoever maintains your site that the update has been applied and the store still works correctly after the upgrade.
composer require drupal/commerce:^2.41 || composer require drupal/commerce:^3.3.13

What it is

From the CVE record

Missing Authorization vulnerability in Drupal Commerce Core allows Forceful Browsing. This issue affects Commerce Core versions: from 0.0.0 to 2.41, from 3.0.0 to 3.3.13.

In plain language

Written by AI from the record

A flaw in the Commerce Core plugin for Drupal online stores could let someone view or access pages they shouldn't by guessing the right web address, but there's no sign anyone is actually doing this, and a fix is already available.

Missing Authorization (CWE-862) in Drupal Commerce Core permits forceful browsing to restricted pages/resources without proper access checks; no exploitation observed in the wild.

If you're affected

  • Unauthorized access to order/customer data
  • Exposure of restricted store pages
  • Reputational risk from data exposure

Exploitation

Where each signal puts this CVE on the scale from published to confirmed exploited.

EPSS13th
CISA KEV

Not in the catalog. CISA has not confirmed exploitation.

Public exploits

No public exploit or proof of concept found in the sources we track.

EPSS

0.2% chance of exploitation activity in the next 30 days, which ranks it in the 13th percentile of scored CVEs.

Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.

Lifecycle

6 events over 0 days, from the signal feeds we watch.

  1. Publishedweakness classified, att&ck mapped, record updated, record updated, record updated

Affected products

Technical detail

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N

Scored 6.5 by NVD.

How it is reached

  • Attack Vector NetworkExploitable remotely over the network without any special conditions
  • Attack Complexity LowNo special conditions — the attack can be reliably reproduced
  • Privileges Required NoneNo authentication required — anyone can exploit this
  • User Interaction NoneNo user interaction needed — fully automated exploitation

Scope

  • Scope UnchangedImpact is limited to the vulnerable component itself

Impact if exploited

  • Confidentiality LowSome restricted information is disclosed, but limited in scope
  • Integrity LowData modification is possible but limited in scope or consequence
  • Availability NoneNo availability impact

Weaknesses

ATT&CK techniques

Mapped from the weaknesses above (CWE to ATT&CK), not observed in attacks.

Sources

Watch the software you run.

My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.

We'll flag the next CVE, public exploit or patch for Commerce Core, not every advisory.