Vulnerability in shopper/framework (CVE-2026-56827)
Summary
Vulnerability in shopper/framework (CVE-2026-56827). Data can be tampered with by attackers. Exploitable via groupedBulkActions. Mitigation: upgrade to 2.9.2 or later.
Original description
The description as published by the source.
Summary
Five Filament groupedBulkActions blocks across the Shopper admin Livewire pages omit the ->authorize(...) permission gate, while their per-record sibling actions (and other Shopper Index pages such as Pages/Settings/Currencies.php, Pages/Reviews/Index.php, Pages/Collection/Index.php, and Pages/Discount/Index.php) correctly chain ->authorize(...). Each affected page's mount() only requires the read-only browse_* permission, so a low-privilege staff user holding only the read permission can drive the bulk endpoint via the standard Livewire callTableBulkAction flow and execute state-mutating operations they were never granted. The vulnerability is the same class as GHSA-f946-9qp6-vgch and GHSA-j328-xmgp-j4q3 (read-only permission gating a write action), just on a different surface (Filament 4 groupedBulkActions rather than top-level Livewire methods).
A staff user holding only browse_attributes can permanently delete every product attribute in the catalog (cascading break of every dependent product variant). A user holding only browse_tags can permanently delete every product tag. Users holding browse_brands, browse_categories, or browse_suppliers can flip the visibility (is_enabled) of every brand/category/supplier in bulk, sabotaging storefront catalog visibility.
CVSS 3.1: AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H = 8.1 High. CWE-285 (Improper Authorization) and CWE-862 (Missing Authorization). The attacker has low privilege (browse…
Source: NIST National Vulnerability Database NVD GitHub Advisory
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-56827 has been found in shopper/framework.
Attackers can target a specific entry point like groupedBulkActions over the network to misuse the product.
Data can be tampered with by attackers. CVSS score: 8.1/10.
What to do: upgrade shopper/framework to 2.9.2 or later.
If unsure, ask your IT team or search "shopper/framework CVE-2026-56827" on the vendor's site.
CVE-2026-56827 (shopper/framework) — CWE-862 / CVSS v3 8.1
Attack vector: remote (network-reachable) / no user interaction
Attack surface: groupedBulkActions / callTableBulkAction / browse_attributes / browse_tags
Patched: 2.9.2 — 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-862) exists in shopper/framework. Attackers reach the vulnerable code path via groupedBulkActions.
Check the vendor advisory for the affected versions of shopper/framework. Attack surface: groupedBulkActions / callTableBulkAction / browse_attributes / browse_tags.
Severity: High (CVSS 8.1/10). Data can be tampered with by attackers.
Update to 2.9.2.
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 'shopper/framework' . 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 'shopper/framework' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
shopper/frameworkを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade shopper/framework to 2.9.2ステージング環境で 2.9.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。