GHSA-c3qp-2ggw-xjg7
CRITICALShopper: Authorization bypass and RBAC privilege escalation in team settings
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
Blast Radius
shopper/frameworkReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.
Description
Impact
Two distinct authorization defects in the team settings allowed any authenticated panel user to take over the RBAC system:
Settings/Team/Indexhad nomount()authorization. Any authenticated user could load the page and use its public actions to create new roles and delete other users, including administrators.Settings/Team/RolePermissiongated its write actions on the read-onlyview_userspermission. Any user holdingview_userscould grant themselves or any other user arbitrary permissions, includingmanage_usersandedit_orders, effectively escalating to full panel administrator from a read-only account.
Combined, these two defects allow a low-privilege authenticated user to obtain administrator privileges and remove the legitimate administrators from the panel.
Patches
Fixed in v2.8.0:
Settings/Team/Index::mount()now authorizes againstmanage_users.Settings/Team/RolePermissionwrite actions now requiremanage_usersinstead ofview_users.
Upgrade via:
composer require shopper/admin:^2.8
Workarounds
None. Upgrade to v2.8.0.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | shopper/framework | all versions | 2.8.0 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for shopper/framework. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update shopper/framework to 2.8.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-c3qp-2ggw-xjg7 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-c3qp-2ggw-xjg7 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to GHSA-c3qp-2ggw-xjg7. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-c3qp-2ggw-xjg7 in your dependencies?
O3 detects GHSA-c3qp-2ggw-xjg7 across Packagist dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.