CVE-2026-62989: Shopper authorization bypass in variant deletion

CVE-2026-62989 · Severity: high · CVSS 8.1 · Published 2026-10-30

Shopper is a headless e-commerce admin panel used to manage product catalogs and inventory. An authenticated staff user with permission to edit products can bypass permission checks and permanently delete product variants without authorization, destroying the catalog and breaking customer storefronts.

Technologies: Shopper Labs Shopper. Vendors: Shopper Labs.

Quick answers

Is CVE-2026-62989 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-62989 being exploited in the wild.
How severe is CVE-2026-62989?
High severity, with a CVSS score of 8.1, published 30 October 2026.
Which products and versions are affected?
Shopper Labs Shopper before 2.10.0.
Is there a fix for CVE-2026-62989?
Yes: fixed in 2.10.0. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-62989 attacked?
It is attacked over the network, in a web application.
Am I affected by CVE-2026-62989?
Check whether you run Shopper Labs Shopper at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • Fixed in: 2.10.0

Technical details

The Variants Livewire component in the admin panel exposes DeleteAction and DeleteBulkAction without server-side authorization checks, allowing an authenticated user with edit_products permission to call callTableAction and callTableBulkAction to delete variants without the required delete_product_variants permission. The vulnerability exists because Filament actions were not explicitly gated at the operation level, relying instead on coarse parent permissions. The fix adds explicit authorization checks to every mutating action across 80 admin Livewire components.

Affected products

  • Shopper Labs Shopper before 2.10.0

Timeline

  • 2026-10-30: disclosed
  • 2026-06-23: patched: fix merged to 2.x branch

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.