GHSA-f946-9qp6-vgch: shopper/framework: Authorization bypass in multiple Livewire admin components
(updated )
Multiple Livewire components in the admin panel allowed an authenticated low-privilege user to mutate data without the required permission:
- Order detail Filament actions (cancel, mark paid, mark complete, capture payment, archive, start processing) were callable with
read_ordersonly and did not requireedit_orders.capturePaymentcould trigger an actual PSP capture. - Order shipments table actions (mark delivered, edit tracking) were callable with
browse_ordersonly. - Sub-form Livewire components for products (Edit, Inventory, Seo, Shipping, Files) had no authorization on
store(), so any authenticated panel user could mutate product data withoutedit_products. Settings/Team/Indexhad nomount()authorization at all — any authenticated user could create roles and delete other users.Settings/Team/RolePermissiongated its write actions on the read-onlyview_userspermission, allowing privilege escalation via the RBAC system itself.PaymentMethods,Currencies,Carrierstable toggles and per-record actions had no per-action permission check.Customers/Create::store()re-passed a Hidden_passwordform field into the create payload.
Several public Eloquent model properties on Livewire components were not #[Locked], allowing client-side ID tampering.
A stored XSS surface existed on the product barcode field, which is rendered through DNS1DFacade::getBarcodeHTML() with {!! !!}.
References
- github.com/advisories/GHSA-f946-9qp6-vgch
- github.com/shopperlabs/shopper/commit/fcd0c5920588702df5b874f432b1042abd77a50b
- github.com/shopperlabs/shopper/issues/510
- github.com/shopperlabs/shopper/pull/511
- github.com/shopperlabs/shopper/releases/tag/v2.8.0
- github.com/shopperlabs/shopper/security/advisories/GHSA-f946-9qp6-vgch
- nvd.nist.gov/vuln/detail/CVE-2026-47740
Code Behaviors & Features
Detect and mitigate GHSA-f946-9qp6-vgch with GitLab Dependency Scanning
Secure your software supply chain by verifying that all open source dependencies used in your projects contain no disclosed vulnerabilities. Dependency Scanning using SBOM also detects vulnerabilities from proprietary advisories that this site does not include. Learn more about Dependency Scanning using SBOM →