Drupal has warned that threat actors are exploiting a “highly critical” security flaw in its Commerce Core component.
The vulnerability, tracked as CVE-2026-118539 (CVSS score: N/A), is a case of missing authorization affecting Commerce Core versions from 0.0.0 to 2.41 and from 3.0.0 to 3.3.13.
“This module enables you to sell goods and services to customers through an included shopping cart and checkout form or through decoupled applications via APIs,” Drupal said in an advisory.
“The module doesn’t sufficiently protect certain routes and entity fields, leading to an access bypass that may financially impact the vendor.”
The open-source content-management framework acknowledged that the vulnerability is being “actively exploited in the wild,” but provided no specifics about the nature of the activity or the extent of the campaign.
Users are being recommended to update to the latest version –
- Version 3.x – Upgrade to Commerce Core 3.3.13
- Earlier versions – Upgrade to Commerce Core 8.x-2.41
Drupal has credited researchers Dan Puccetti (dpuccetti), Marcus Johansson (marcus_johansson), and Robert Snyder (rsnyd) with reporting the flaw.
The development comes as two critical vulnerabilities in PHP, tracked as CVE-2026-109618 and CVE-2026-109619 (CVSS scores: 9.2), and collectively referred to as PHP2Shell, are witnessing active exploitation attempts in the wild.
As of October 25, the percentage of organizations significantly affected by PHP2Shell has declined to 52.1%, according to data from Google-owned Wiz.
The cloud security company said it has so far observed two types of activities, including attempts using the PHP2Shell exploit mechanism that match public proof-of-concept (PoC) exploits.
The other category refers to “PHP2Shell-branded tools unrelated to the vulnerabilities that instead relied on session poisoning and a separate local file inclusion (LFI) vulnerability in the application,” Wiz researchers Yaara Shriki, Shahar Dorfman, Alma Blachsan, and Yaron Samuel said.
“Our observations show that triggering memory exhaustion alone is not enough to complete the exploit chain. Differences in PHP builds, memory limits and worker behavior can prevent subsequent stages from working. The challenge for opportunistic attackers is turning currently available public PoCs into similarly reliable operational tooling or developing it on their own.”
