On this page (7 sections)
Drupal has warned that a missing authorization flaw in its Commerce Core module, tracked as CVE-2026-118539, is being exploited in the wild, according to The Hacker News. In Drupal's words as quoted there, the module does not sufficiently protect certain routes and entity fields, which may financially impact the store operator.
If you run an online store on Drupal Commerce, treat this as a patch-now item. The upgrade targets reported in that coverage are Commerce Core 3.3.13 and 8.x-2.41, but the version numbers in the sources overlap with the affected ranges, so read the section on affected versions carefully and confirm against Drupal's advisory.
What happened
On October 30, 2026 the flaw was published to the GitHub Advisory Database, which references Drupal's contributed-module advisory, SA-CONTRIB-2026-254. The GitHub advisory describes it as a missing authorization vulnerability in Commerce Core that allows forceful browsing.
The Hacker News reports that Drupal acknowledged the vulnerability is being "actively exploited in the wild" but gave no specifics about the activity or how widespread it is. Drupal credited researchers Dan Puccetti, Marcus Johansson and Robert Snyder with the report. We could not review the Drupal advisory text directly, so the exploitation and upgrade-version details here rely on that report.
Why the severity labels differ
The sources do not agree on a single rating. The GitHub advisory shows a CVSS 6.5 (Moderate) score with network attack vector, low complexity, no privileges and no user interaction, and low impact to confidentiality and integrity. Drupal's own risk language, quoted in the news report, is "highly critical", and that report lists no CVSS score. Treat the CVSS number as a generic technical rating and the exploitation report as the reason to move quickly.
- CVSS v3.1 base score in the GitHub advisory
- 6.5
- EPSS score (52nd percentile) at time of the advisory
- 0.671%
Technical details
Missing authorization (CWE-862) means the application does not check whether the caller is allowed to reach a resource or perform an action. In practice, a request that should be refused is simply served. The GitHub advisory labels this case "forceful browsing", meaning reaching pages or endpoints directly, without going through the intended flow or permission check.
The wording about routes and entity fields comes from Drupal's description as quoted by The Hacker News: the module "doesn't sufficiently protect certain routes and entity fields, leading to an access bypass that may financially impact the vendor." The same quote describes the module as serving customers through a cart and checkout form or through decoupled applications via APIs. The research does not say which routes or fields are affected, and we are not aware of public technical details beyond that. Both the storefront and API surfaces are worth reviewing.
Who is affected
Any Drupal site with Commerce Core in the ranges 0.0.0 to 2.41 or 3.0.0 to 3.3.13 is listed as affected by the CVE record and GitHub advisory.
Realistic exposure is highest for public-facing stores, since the CVSS vector indicates the issue can be reached over the network without login. Sites that do not use Commerce Core are not affected by this specific CVE.
How to check your exposure
Start by finding the installed Commerce version. If you manage your site with Composer, this read-only command lists the installed package version (run from the project root; look for the version number in the output):
composer show drupal/commerceIf you have Drush available, this lists enabled modules and versions so you can find the Commerce entries (look for the commerce rows and compare to the versions above):
drush pm:list --status=enabled | grep -i commerceYou can also review the Available updates report in the Drupal admin interface, which flags security updates for contributed modules.
What to do now
- Identify your Commerce Core version using the commands above or the Available updates report.
- Read SA-CONTRIB-2026-254 for the authoritative fixed version, since the sources overlap on version numbers.
- Back up the database and codebase, and test the update on a staging copy if you can.
- Update to the newest available Commerce Core release, and at minimum to 3.3.13 on the 3.x line or 8.x-2.41 on earlier versions, as reported by The Hacker News.
- Clear caches and run database updates after deploying, then test cart, checkout and any API clients.
- Review recent orders, payments, prices, promotions and user or role changes for anything unexpected, since exploitation may have financial impact.
- Check web server and application logs for unusual direct requests to commerce routes or API endpoints, and for requests from unfamiliar addresses.
- If you find signs of tampering, follow an incident process: rotate admin and API credentials, and review payment and order records.
A typical Composer update looks like the following. It changes code on the server, so run it on staging first and keep a backup.
composer update drupal/commerce --with-all-dependencies
drush updatedb
drush cache:rebuildDetection and monitoring
Because the exploitation details are not public, focus on outcomes. Watch for orders or payment states that changed without a matching customer action, altered product prices or promotions, and new or modified accounts. Keep access logs long enough to look back to at least October 30, 2026, when the issue became public, and earlier if you can.
After patching, keep an eye on your store's exposure over time. Webforta Scan can run read-only security scans of sites you verify, and Webforta Monitor tracks uptime, certificate, DNS and header changes. Neither replaces applying the vendor update. If you run a store, the online store security guide covers broader hardening.
Timeline
| Date | Event |
|---|---|
| Oct 30, 2026 | CVE-2026-118539 published; GitHub advisory GHSA-372m-625x-8m53 published and updated |
| Oct 30, 2026 | The Hacker News reports Drupal's warning of active exploitation and the upgrade versions |
Sources
This article is based on the public sources below. Details can change as vendors and researchers publish more; check the original advisories before acting on version numbers.
