/

CVE-2026-56825

Severity:

HIGH RISK

(8.1)

Missing Authorization (CWE-862) in Shopper Admin Panel

CVE-2026-56825

Deferred

Vulnerability type

Category:

Missing Authorization

CWE:

CWE-862

Impact:

Unauthorized Collection and Catalog Modification

Severity:

HIGH RISK

(8.1)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

Shopper's Admin Panel permits certain authenticated staff users to remove products from collections without the required collection-deletion authorization. Because the collection identifier can also be client-modified, a user with limited browsing access may alter arbitrary collections, disrupting catalog pages and promotions.

Affected context

The issue occurs in the Livewire collection-products component when deletion and bulk-removal actions are exposed without checking the delete_collections permission. It is particularly risky when an authenticated staff user has only browsing privileges, while the public collection property remains mutable through client-controlled component state.

Exploit preconditions

  • Attack surface: Authenticated administrative Livewire component
  • Required access: A staff account with limited collection-browsing privileges
  • Trigger point: Product removal or bulk deletion actions in the collection interface
  • Manipulated input: The client-controlled collection identifier
  • Why exploitation is possible: Destructive actions do not consistently enforce the authorization required to delete or modify collections, and the target collection reference is not protected from client-side substitution

Why this happens

The underlying bug is an authorization failure mapped to CWE-862: Missing Authorization. Destructive operations are exposed without enforcing the permission appropriate to the requested action. The risk is increased by treating a public, client-modifiable component property as a trusted reference to the collection being changed, rather than locking and reauthorizing that target on the server.

Potential impact

  • An unauthorized staff user may detach products from collections
  • A user could empty a targeted collection
  • Catalog landing pages may display incomplete or incorrect product sets
  • Promotions associated with affected collections could be disrupted
  • Collection data integrity and administrative trust may be reduced

General mitigation guidance

Mitigation generally focuses on enforcing authorization at every destructive operation and reducing trust in client-controlled state.

Common defensive patterns include:

  • Apply server-side permission checks directly to delete and bulk-removal handlers
  • Require the specific collection-management capability rather than relying on general browse access
  • Lock or otherwise avoid exposing server-authoritative collection identifiers as mutable client state
  • Re-fetch and reauthorize the target collection immediately before modification
  • Validate that selected products belong to the authorized collection and tenant context
  • Follow least-privilege principles for staff roles and administrative actions

How teams detect issues like this

Organizations can identify similar issues through:

  • Static analysis rules that flag destructive handlers without nearby authorization checks
  • Code review searches for public or client-mutable identifiers used in database mutations
  • Tests that exercise each administrative action with progressively limited roles
  • Policy checks requiring authorization at service or controller boundaries, not only in the user interface
  • Audit logging and alerting for bulk removals, unexpected collection targets, and denied or anomalous administrative actions
  • Automated security review tools that inspect Livewire components and authorization middleware usage

Sources

SourceLink
github.comgithub.com/shopperlabs/shopper/commit/bf72e2753e21296184596d507336c7d65ecd46ff
github.comgithub.com/shopperlabs/shopper/pull/570
github.comgithub.com/shopperlabs/shopper/releases/tag/v2.9.2
github.comgithub.com/shopperlabs/shopper/security/advisories/GHSA-2cg9-97gq-9mqp

Frequently asked

questions

Yes, within the application's authenticated administrative surface. The attacker must be able to reach and invoke the relevant Livewire actions.

No. The described condition involves a staff user with limited browsing permission; broader collection-deletion privileges should not be necessary when authorization is missing from the action.

Enforce the required authorization on the server for every destructive action, lock server-owned identifiers, and revalidate the target collection before applying changes.

Use deny-by-default role policies, test destructive operations with low-privilege accounts, avoid trusting client-mutable object references, and monitor bulk administrative changes.

Find out what's already
exploitable in your codebase.