/

CVE-2026-56827

Severity:

HIGH RISK

(8.1)

Broken Access Control (CWE-862) in Shopper Admin Panel

CVE-2026-56827

Deferred

Vulnerability type

Category:

Missing Authorization

CWE:

CWE-862

Impact:

Unauthorized bulk modification and deletion of catalog data

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 administrative bulk-action handlers do not consistently enforce server-side authorization for staff users who have only browse-level permissions. A browse-only user may therefore mass-delete attributes or tags and change visibility for attributes, brands, categories, or suppliers, potentially disrupting the storefront catalog.

Affected context

The issue occurs in Shopper's admin panel on grouped bulk-action controls for attribute, tag, brand, category, and supplier pages. These pages may be accessible with browse-level permissions, while the associated bulk operations require stronger authorization that is not enforced consistently on the server. Per-record actions and the advisory-identified comparison pages are not affected.

Exploit preconditions

  • Attack surface: Shopper's authenticated administrative web interface
  • Required access: A staff account with browse-only permission for the relevant resource
  • Trigger point: Invocation of grouped bulk actions on the affected browse pages
  • Why exploitation is possible: The page-level browse permission is checked, but the server-side handlers do not independently authorize destructive deletion or visibility-changing operations

Why this happens

The underlying bug is an authorization gap in grouped bulk-action handlers. The application relies on permission checks that are sufficient to display or browse a page but does not enforce operation-specific authorization before performing bulk deletion or visibility changes. This behavior maps to CWE-862: Missing Authorization, because a user can perform actions outside the privileges granted by their role.

Potential impact

  • Unauthorized deletion of attributes or tags may occur
  • Product variants could be broken by mass deletion of related attributes
  • Catalog visibility for brands, categories, suppliers, or attributes may be changed
  • Storefront product discovery and merchandising could be substantially disrupted
  • Business operations and catalog integrity could be impaired

General mitigation guidance

Mitigation generally focuses on enforcing authorization at the operation boundary rather than relying on page access or client-side controls.

Common defensive patterns include:

  • Applying server-side, action-specific permission checks to every bulk operation
  • Separating browse, update, visibility-management, and delete privileges
  • Revalidating authorization for each requested resource and operation
  • Failing closed when permissions are missing or ambiguous
  • Limiting bulk operations through least-privilege roles and explicit administrative policies
  • Recording authorization decisions and bulk changes for audit and recovery

How teams detect issues like this

Organizations can identify similar issues through:

  • Static analysis that maps routes, Livewire actions, and handlers to authorization checks
  • Code review searches for bulk-action definitions lacking explicit policy or permission enforcement
  • Tests that exercise destructive and state-changing actions with browse-only accounts
  • Authorization matrices covering page access separately from operation access
  • Runtime monitoring for unusual bulk deletions or large-scale visibility changes
  • Policy checks requiring server-side authorization for every mutation endpoint and action

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-243p-f3cv-c5wh

Frequently asked

questions

Yes. A staff user who can access an affected browse page may be able to invoke unauthorized grouped bulk actions despite lacking stronger modification or deletion privileges.

No. The described scenario requires an authenticated staff account with browse-level access to a relevant admin page.

Enforce operation-specific authorization on the server for every grouped bulk action, including deletion and visibility changes, rather than relying only on page-level browse permissions.

Maintain an explicit permission matrix, test each action with least-privilege roles, and require server-side policy checks for all state-changing operations.

Find out what's already
exploitable in your codebase.