# Shopper: Authorization bypass and RBAC privilege escalation in team settings

Advisory record · `GHSA-c3qp-2ggw-xjg7`

- **Identifiers:** `GHSA-c3qp-2ggw-xjg7` · `CVE-2026-47744` · `PKSA-5g52-7x8y-w2y1`
- **State:** Confirmed
- **Severity:** CVSS 9.9 Critical
- **Critical:** Yes: CVSS 9+
- **Weakness (CWE):** [CWE-269](https://cwe.mitre.org/data/definitions/269.html) · [CWE-285](https://cwe.mitre.org/data/definitions/285.html)
- **Tags:** [Privilege escalation](https://agentprime.io/advisories/tag/privilege-escalation.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.

## Critical

Critical, because:

- CVSS score 9.9: 9.0 or more.

How we decide what’s critical: <https://agentprime.io/advisories/critical.md>

## 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's Packagist package shopper/framework is affected in versions before 2.8.0. In the team settings, a missing authorization check on the team page and a write-permission check tied to the read-only view_users permission let any authenticated panel user, including one holding only view_users, create roles, delete users, and grant arbitrary permissions, including administrator rights. Upgrade to shopper/framework 2.8.0, which adds the missing checks and requires manage_users for the affected write actions; the source lists no workaround.

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

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

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

## Timeline

- 31 Oct 2026, 13:57 UTC: First seen by agentprime
- 31 Oct 2026, 13:57 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-c3qp-2ggw-xjg7)

## Sources

- [GitHub Advisory Database: GHSA-c3qp-2ggw-xjg7](https://github.com/advisories/GHSA-c3qp-2ggw-xjg7)
- [OSV: GHSA-c3qp-2ggw-xjg7](https://osv.dev/vulnerability/GHSA-c3qp-2ggw-xjg7)
- <https://github.com/shopperlabs/shopper/security/advisories/GHSA-c3qp-2ggw-xjg7>
- <https://nvd.nist.gov/vuln/detail/CVE-2026-47744>
- <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-c3qp-2ggw-xjg7>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-c3qp-2ggw-xjg7/>. Everything for agents: <https://agentprime.io/llms.txt>.