/

CVE-2026-56829

Severity:

HIGH RISK

(8.1)

Missing Authorization (CWE-862) in Shopper Admin Panel

CVE-2026-56829

Deferred

Vulnerability type

Category:

Missing Authorization

CWE:

CWE-862

Impact:

Unauthorized inventory modification and business logic abuse

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 product variant stock component may allow authenticated admin-panel users without inventory-editing permission to change stock levels for arbitrary variants and inventory locations. The issue becomes risky when component state can be modified by the client and the stock adjustment action does not enforce the required authorization check.

Affected context

The vulnerability occurs in Shopper's Livewire product variant stock component when stock adjustments are exposed without enforcing the edit_product_variants authorization requirement. Deployments may be affected when lower-privileged staff accounts can access the admin panel and the component's public variant state remains client-controlled rather than being protected from tampering.

Exploit preconditions

  • Attack surface: Authenticated Shopper admin-panel functionality
  • Required access: A valid admin-panel account, including an account with only browse_products access
  • Trigger point: Submission of the product variant stock adjustment action
  • Required state control: The client must be able to influence the selected variant or inventory location through mutable component state
  • Why exploitation is possible: The action does not independently enforce the edit_product_variants authorization requirement, allowing authorization boundaries to be bypassed

Why this happens

The underlying bug is a missing authorization check in a state-changing operation, which maps to CWE-862, Missing Authorization. The component also exposes security-relevant selection state as client-mutable data without an equivalent server-side integrity control. Treating client-provided component state as trusted allows a lower-privileged user to direct an inventory adjustment beyond the scope of the user's intended permissions.

Potential impact

  • An unauthorized user may inflate inventory quantities
  • An unauthorized user may reduce stock or force variants into an out-of-stock state
  • Inventory records for variants outside the user's visible page may be altered
  • Product availability, order fulfillment, and stock reporting could be disrupted
  • Business losses or inventory data integrity issues could result

General mitigation guidance

Mitigation generally focuses on enforcing authorization at the server-side

operation boundary rather than relying on component visibility or navigation

restrictions.

Common defensive patterns include:

  • Require the appropriate product-variant editing permission inside every stock-changing action
  • Reauthorize the selected variant and inventory location immediately before applying a change
  • Treat all client-controlled component properties as untrusted input
  • Use server-derived identifiers and locked or otherwise integrity-protected state for security-relevant fields
  • Validate quantity adjustments against business rules, permitted ranges, and the caller's scope
  • Apply least privilege to staff roles and separate browse access from modification access
  • Record and monitor inventory changes with actor, target, and authorization context

How teams detect issues like this

Detection can combine:

  • Static analysis for state-changing handlers that lack authorization or policy checks
  • Code review searches for public client-bound properties representing resource identifiers or permissions
  • Tests that invoke mutation actions using each supported role, including browse-only accounts
  • Policy checks requiring authorization immediately before inventory, pricing, or other business-critical writes
  • Runtime audit monitoring for stock changes by users without the corresponding edit permission

Automated code-review and security-analysis tools may help identify unguarded mutation paths, but business-role tests are still important.

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-g3f9-g5vj-p62f

Frequently asked

questions

Any authenticated admin-panel user whose role permits access to the affected

component may be in scope, including staff accounts intended only to browse

products, if server-side authorization is not enforced for the stock action.

No. The described attack requires an authenticated admin-panel session, but

it may still have broad business impact because a lower-privileged account

can affect inventory outside its intended permissions.

Enforce the required authorization policy within the server-side stock mutation

handler, recheck access to the selected variant and location, and treat

client-controlled component state as untrusted.

Separate read and write permissions, protect security-sensitive component state,

validate all resource references on the server, and test every state-changing

action against the full role and permission matrix.

Find out what's already
exploitable in your codebase.