Is CVE-2026-47744 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-47744 being exploited in the wild.

How severe is CVE-2026-47744?

Critical severity, with a CVSS score of 9.9, 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-47744?

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-47744 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-47744?

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.

CVE-2026-47744: Shopper Labs Shopper privilege escalation in team settings

Q: Is there a fix for CVE-2026-47744?

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.

Q: How is CVE-2026-47744 attacked?

It is attacked over the network, in a software library.

Q: Am I affected by CVE-2026-47744?

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.

CVE-2026-47744 · Severity: critical · CVSS 9.9 · Published 2026-05-29

Shopper is an e-commerce administration panel. A security flaw in the team management settings allows any logged-in user to bypass security checks to create new roles or delete other users, including administrators. This could allow a low-level user to take full control of the store, access customer data, and lock out legitimate staff.

Technologies: shopper/framework (Packagist). Vendors: Packagist.

Quick answers

Is CVE-2026-47744 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-47744 being exploited in the wild.
How severe is CVE-2026-47744?: Critical severity, with a CVSS score of 9.9, 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-47744?: 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-47744 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-47744?: 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

The vulnerability consists of two defects in the Shopper RBAC system. First, the `Settings/Team/Index` component lacked a `mount()` authorization check, allowing any authenticated user to access public actions such as role creation and user deletion. Second, `Settings/Team/RolePermission` incorrectly used the read-only `view_users` permission to gate write actions, allowing users with minimal view rights to grant themselves administrative permissions like `manage_users`. An attacker with any valid account can exploit these to escalate to full administrator privileges. The issue is resolved in version 2.8.0 by implementing proper authorization checks against the `manage_users` permission.

Affected products

Shopper Labs Shopper Framework < 2.8.0

Identifiers

CVE-2026-47744
GHSA-c3qp-2ggw-xjg7

Timeline

2026-05-20: disclosed: Initial report by baradika
2026-05-29: advisory: NVD publication date
2026-06-05: patched: GitHub Advisory published and fix confirmed in v2.8.0

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.