# Shopper: Multiple data integrity and disclosure issues in admin Livewire components

Advisory record · `GHSA-hr9v-r8r2-hg7j`

- **Identifiers:** `GHSA-hr9v-r8r2-hg7j` · `CVE-2026-47743` · `PKSA-88dm-mp91-mkr8`
- **State:** Confirmed
- **Severity:** CVSS 8.7 High
- **Critical:** No
- **Weakness (CWE):** [CWE-79](https://cwe.mitre.org/data/definitions/79.html) · [CWE-200](https://cwe.mitre.org/data/definitions/200.html) · [CWE-639](https://cwe.mitre.org/data/definitions/639.html)
- **Tags:** [Cross-site scripting (XSS)](https://agentprime.io/advisories/tag/xss.md) · [Information disclosure](https://agentprime.io/advisories/tag/info-disclosure.md) · [Broken access control](https://agentprime.io/advisories/tag/access-control.md)
- **Published:** 5 Jun 2026
- **Updated:** 10 Sept 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 5 Jun 2026, 20:35 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`; fixed in `2.8.0`

## Machine-written summary

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

> Shopper framework versions before 2.8.0 contain three related defects in admin Livewire components. An authenticated user can change record IDs to reach other records, a plaintext password is echoed back in a hidden form field during customer creation, and a user with edit_products permission can store a script in the product barcode that runs for other admins. Upgrade to shopper/framework 2.8.0, which fixes all three; the source lists no workarounds.

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.7 High, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:N`, from CNA (GitHub_M)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0038, the 33rd percentile, on 16 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 14:00 UTC: First seen by agentprime
- 31 Oct 2026, 14:00 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-hr9v-r8r2-hg7j)

## Sources

- [GitHub Advisory Database: GHSA-hr9v-r8r2-hg7j](https://github.com/advisories/GHSA-hr9v-r8r2-hg7j)
- [OSV: GHSA-hr9v-r8r2-hg7j](https://osv.dev/vulnerability/GHSA-hr9v-r8r2-hg7j)
- <https://github.com/shopperlabs/shopper/security/advisories/GHSA-hr9v-r8r2-hg7j>
- <https://github.com/shopperlabs/shopper/pull/511>
- <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-hr9v-r8r2-hg7j>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-hr9v-r8r2-hg7j/>. Everything for agents: <https://agentprime.io/llms.txt>.
