Quick answers
- Is CVE-2026-47745 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-47745 being exploited in the wild.
- How severe is CVE-2026-47745?
- Medium severity, with a CVSS score of 6.5, published 29 May 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-47745?
- 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-47745 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-47745?
- 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
A missing authorization vulnerability (CWE-862) exists in the Shopper admin panel. The application rendered inline toggles and per-record actions (enable, disable, edit, delete) for PaymentMethods, Currencies, and Carriers without verifying if the authenticated user possessed the required granular permissions. An attacker with low-level authenticated access to the admin panel could exploit this to perform unauthorized state changes, leading to a denial of service for the checkout process or loss of pricing integrity. The issue is resolved in version 2.8.0 by implementing explicit permission checks (edit_payment_methods, edit_currencies, edit_carriers) for these actions.
Affected products
- Shopper Labs Shopper Framework < 2.8.0
Identifiers
- CVE-2026-47745
- GHSA-fxqw-97cc-7g5c
Timeline
- 2026-05-20: disclosed: Initial disclosure by reporter
- 2026-05-29: advisory: NVD publication date
- 2026-06-05: patched: GitHub Advisory published and fix confirmed in v2.8.0