Vulnerability in drupal/basket (CVE-2026-9726)
Summary
Vulnerability in drupal/basket (CVE-2026-9726). Successful exploitation can lead to full system takeover. Mitigation: upgrade to 2.1.17 or later.
Original description
The description as published by the source.
The Basket module enables e-commerce and checkout functionality for Drupal sites.
The module does not sufficiently sanitize user-supplied data before passing it to PHP's unserialize().
An attacker can supply a crafted payload and trigger PHP Object Injection. If a viable gadget chain exists in the site codebase or installed dependencies, this can result in arbitrary PHP code execution.
Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-9726 has been found in drupal/basket.
Successful exploitation can lead to full system takeover. CVSS score: 9.8/10.
What to do: upgrade drupal/basket to 2.1.17 or later.
If unsure, ask your IT team or search "drupal/basket CVE-2026-9726" on the vendor's site.
CVE-2026-9726 (drupal/basket) — CWE-915 / CVSS v3 9.8
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 2.1.17 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-915) exists in drupal/basket.
Check the vendor advisory for the affected versions of drupal/basket.
Severity: Critical (CVSS 9.8/10). Successful exploitation can lead to full system takeover.
Update to 2.1.17.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'drupal/basket' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'drupal/basket' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
drupal/basketを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade drupal/basket to 2.1.17ステージング環境で 2.1.17 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- web drupal.org
- web nvd.nist.gov
- web github.com