Is CVE-2026-56825 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-56825 being exploited in the wild.

How severe is CVE-2026-56825?

High severity, with a CVSS score of 8.1, published 15 September 2026.

Which products and versions are affected?

shopper/framework (Packagist) < 2.9.2, ECOSYSTEM:introduced=0,fixed=2.9.2; Shopper Labs Shopper < 2.9.2.

Is there a fix for CVE-2026-56825?

Yes. shopper/framework (Packagist): upgrade to 2.9.2 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-56825 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-56825?

Check whether you run shopper/framework (Packagist) or 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.

CVE-2026-56825: Shopper CollectionProducts missing authorization on product removal

Q: Is there a fix for CVE-2026-56825?

Yes. shopper/framework (Packagist): upgrade to 2.9.2 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Q: How is CVE-2026-56825 attacked?

It is attacked over the network, in a software library.

Q: Am I affected by CVE-2026-56825?

Check whether you run shopper/framework (Packagist) or 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.

CVE-2026-56825 · Severity: high · CVSS 8.1 · Published 2026-09-15

The Shopper e-commerce platform's collection management interface lacks proper authorization controls on product removal actions. An authenticated staff member with only basic "browse collections" permission can remove any product from any collection in the database, including collections they have never accessed. This allows an insider to silently break product groupings that drive storefront categories and promotional campaigns.

Technologies: shopper/framework (Packagist), Shopper Labs Shopper. Vendors: Packagist, Shopper Labs.

Quick answers

Is CVE-2026-56825 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-56825 being exploited in the wild.
How severe is CVE-2026-56825?: High severity, with a CVSS score of 8.1, published 15 September 2026.
Which products and versions are affected?: shopper/framework (Packagist) < 2.9.2, ECOSYSTEM:introduced=0,fixed=2.9.2; Shopper Labs Shopper < 2.9.2.
Is there a fix for CVE-2026-56825?: Yes. shopper/framework (Packagist): upgrade to 2.9.2 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-56825 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-56825?: Check whether you run shopper/framework (Packagist) or 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

shopper/framework (Packagist): upgrade to 2.9.2 or later
```
composer require shopper/framework:^2.9.2
```

Technical details

The vulnerability is a missing authorization check (CWE-862) in the Filament component located at packages/admin/src/Livewire/Components/Collection/CollectionProducts.php. Two distinct code paths lack authorization: the per-record Action::make('delete') at line 73 and the DeleteBulkAction::make() at line 91, neither carrying an ->authorize(...) method chain. Additionally, the public Collection $collection property at line 40 lacks the #[Locked] attribute, allowing client-side modification of the collection ID in Livewire wire payloads. An authenticated user can exploit this by crafting a POST request to /shopper/livewire/update, injecting an arbitrary collection ID and product ID list into the component snapshot, and invoking callBulkAction or the per-record delete. The required privilege level is minimal: only browse_collections, not edit_collections. The fix requires adding #[Locked] to the property and ->authorize('edit_collections') to both delete actions; patched in version 2.9.2.

Affected products

Shopper Labs Shopper < 2.9.2

Identifiers

CVE-2026-56825
GHSA-2cg9-97gq-9mqp

Timeline

2026-09-11: disclosed: Published to GitHub Advisory Database
2026-09-11: patched: Fix released in version 2.9.2

References

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