# Shopper: privilege escalation via improper Livewire admin component authorization

Advisory record · `GHSA-j328-xmgp-j4q3`

- **Identifiers:** `GHSA-j328-xmgp-j4q3` · `CVE-2026-56828` · `PKSA-5w3n-c3b1-mxqj`
- **State:** Confirmed
- **Severity:** CVSS 8.8 High
- **Critical:** No
- **Weakness (CWE):** [CWE-285](https://cwe.mitre.org/data/definitions/285.html) · [CWE-862](https://cwe.mitre.org/data/definitions/862.html)
- **Tags:** [Broken access control](https://agentprime.io/advisories/tag/access-control.md)
- **Published:** 11 Sept 2026
- **Updated:** 11 Sept 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 11 Sept 2026, 21:28 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `shopper/framework` (Packagist): affected `>=2.8.0, <2.9.2`; fixed in `2.9.2`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> Shopper's shopper/framework Packagist package, versions 2.8.0 up to but not including 2.9.2, has missing authorization checks in three Livewire admin components. A staff user who holds only the view_users permission (and access_dashboard) could change team permissions, create a new admin team member with a chosen password, or delete roles and permissions, which allows privilege escalation. The fix is to upgrade shopper/framework to 2.9.2, which is the fixed version listed in the source.

Written 31 Oct 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 8.8 High, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`, from CNA (GitHub_M)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0044, the 38th percentile, on 17 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 28 Oct 2026, 15:40 UTC: [Confirmed by the CVE List](https://www.cve.org/CVERecord?id=CVE-2026-56828)
- 28 Oct 2026, 16:17 UTC: [Confirmed by NVD](https://nvd.nist.gov/vuln/detail/CVE-2026-56828)
- 31 Oct 2026, 13:56 UTC: First seen by agentprime
- 31 Oct 2026, 13:56 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-j328-xmgp-j4q3)

## Sources

- [GitHub Advisory Database: GHSA-j328-xmgp-j4q3](https://github.com/advisories/GHSA-j328-xmgp-j4q3)
- [OSV: GHSA-j328-xmgp-j4q3](https://osv.dev/vulnerability/GHSA-j328-xmgp-j4q3)
- <https://github.com/shopperlabs/shopper/security/advisories/GHSA-j328-xmgp-j4q3>
- <https://github.com/shopperlabs/shopper>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-j328-xmgp-j4q3>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-j328-xmgp-j4q3/>. Everything for agents: <https://agentprime.io/llms.txt>.
