Quick answers
- Is CVE-2026-47743 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-47743 being exploited in the wild.
- How severe is CVE-2026-47743?
- High severity, with a CVSS score of 8.7, published 23 July 2026.
- Which products and versions are affected?
- shopper/framework (Packagist) < 2.8.0, ECOSYSTEM:introduced=0,fixed=2.8.0.
- Is there a fix for CVE-2026-47743?
- Yes. shopper/framework (Packagist): upgrade to 2.8.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-47743 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-47743?
- Check whether you run shopper/framework (Packagist) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- shopper/framework (Packagist): upgrade to 2.8.0 or later
composer require shopper/framework:^2.8.0
Technical details
Shopper (shopper/framework) prior to version 2.8.0 contains three primary security defects in its admin Livewire components. First, an Insecure Direct Object Reference (IDOR) exists because several components exposed Eloquent model identifiers as public properties without the #[Locked] attribute, allowing authenticated users to manipulate record IDs in the wire payload. Second, the Customers/Create component leaked plaintext passwords by passing them through a hidden form field, exposing them in the DOM and Livewire snapshots. Third, a stored Cross-Site Scripting (XSS) vulnerability exists in the product barcode field due to unescaped rendering via DNS1DFacade::getBarcodeHTML(). An attacker with 'edit_products' permissions could inject malicious scripts to target other administrators. These issues are resolved in version 2.8.0.
Affected products
- shopperlabs shopper/framework < 2.8.0
Identifiers
- CVE-2026-47743
- GHSA-hr9v-r8r2-hg7j
Timeline
- 2026-05-11: patched: Fixes merged in pull request 511
- 2026-05-20: advisory: GitHub Security Advisory published
- 2026-07-23: disclosed: CVE published to NVD