CVE-2026-47743 is a high-severity (CVSS 8.7) Cross-site Scripting (XSS) vulnerability in shopper/framework. A fix is available for shopper/framework — see the affected versions and patch details below.
Shopper: Multiple data integrity and disclosure issues in admin Livewire components
Exploitation Status
No confirmed exploitation observed yet
- A successful exploit gives an attacker total control of the affected component, not partial access.
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2026-47743.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
CVE-2026-47743 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.
Where this sits among everything scored
Of 390,807 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.
Real-World Exposure
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
Three related defects on admin Livewire components allowed data tampering, sensitive data disclosure, and stored XSS:
- IDOR via unlocked properties. Several Livewire components in the admin panel exposed Eloquent model identifiers as public properties without the
#[Locked]attribute. An authenticated user could rewrite the wire payload from the browser to target any record id, bypassing the implicit scoping enforced by the page routing. - Sensitive data echoed back through Hidden form field.
Customers/Create::store()re-passed aHidden_passwordform field straight into the create payload. The plaintext password was rendered into the HTML and transported through the Livewire snapshot in clear text, exposing credentials in the page DOM and in any logging that captures Livewire payloads. - Stored XSS on product barcode. The product barcode field was rendered through
DNS1DFacade::getBarcodeHTML()with{!! !!}. An attacker withedit_productspermission could persist malicious payload in the barcode field that would execute in the browser of any admin user viewing that product, enabling session theft and privileged-action chaining.
Patches
Fixed in v2.8.0:
- All vulnerable Livewire model identifiers are now marked
#[Locked]. Customers/Createno longer round-trips the password through a Hidden form field; the plaintext password is hashed at action boundary and never returned to the client.- The product barcode rendering now escapes the value before passing it to the barcode generator and the output is wrapped in an
<svg>context that does not interpret event handlers.
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.0composer require shopper/framework:^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, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update shopper/framework to 2.8.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-47743 is resolved across your whole dependency graph.
Workarounds
Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.
Frequently Asked Questions
Is CVE-2026-47743 in your dependencies?
Find it across Packagist, including transitive dependencies.