Shopper is a Headless e-commerce Admin Panel. Prior to 2.8.0, three related defects on admin Livewire components allowed data tampering, sensitive data disclosure, and stored XSS. First, 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. Second, Customers/Create::store() re-passed a Hidden _password form 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. Finally, the product barcode field was rendered through DNS1DFacade::getBarcodeHTML() with {!! !!}. An attacker with edit_products permission 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. Starting in v2.8.0, all vulnerable Livewire model identifiers are now marked #[Locked]; Customers/Create no longer round-trips the password through a Hidden form field; the plaintext password is hashed at action boundary and never returned to the client; and the product barcode rendering now escapes the value before passing it to the barcode generator and the output is wrapped in an `` context that does not interpret event handlers. No known workarounds are available.
CVE-2026-47743
“—” beside the score: it is equal to the CVSS score beside it.
Score 8.7 from GitHub Security Advisory (severity: HIGH) published 2026-06-05. A secondary CVSS source baseline 8.7; sources differ by 0.0.
Also known asEUVD-2026-48336 (ENISA EUVD) · GHSA-hr9v-r8r2-hg7j (GitHub Security Advisories)Source: ENISA EUVD
- High severity, but no confirmed exploitation yet
A fix is available — apply it.
- CVSS v3
- 8.7
- EG Score
- 8.7HIGHmedium confidence
- EG Risk
- 39EG Risk 39/100
EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.
How it’s computed (value × EchelonGraph’s weight)Severity87% × 45%Impact severity (EG Severity): CVSS 8.7 of 10. Never the KEV-floored or EPSS-lifted EG Score.Exploitation0.4% × 40%FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.Automatability0% × 15%CISA's SSVC Automatable value: no (Vulnrichment).SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.Action: A fix is available. Apply it within your standard update timelines. - EPSS PROB
- 0.4%
- EPSS %ILE
- 32nd
- KEV
- Not listed
What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)
The EG score (8.7): severity, escalated by confirmed exploitation. This CVE's 8.7 is its impact severity (EG Severity), not escalated.
- EG Severity
- 8.7 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
- EG Likelihood
- 0.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-31). FIRST's exploitation probability, not an EchelonGraph model.
- Confirmed exploitation
- None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
- EG Priority
- SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.
SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).
A fix is available. Apply it within your standard update timelines.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table
BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.
The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it
Published
June 5, 2026
Last Modified
October 24, 2026
Advisory Details (2)
Auto-updated Jul 23, 2026fix(security): authorization bypass and discount race in cart/checkout
Patch available: shopperlabs/shopper v2.8.0 (PR #511 merged 2026-05-11)
https://github.com/shopperlabs/shopper/pull/511Multiple data integrity and disclosure issues in admin Livewire components · Advisory · shopperlabs/shopper · GitHub
https://github.com/shopperlabs/shopper/security/advisories/GHSA-hr9v-r8r2-hg7jVendor Advisories for CVE-2026-47743(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Patch Availability(1)
| Vendor / Ecosystem | Fix (by version range) / Patch | Released | Source |
|---|---|---|---|
| composer | shopper/framework @ 2.8.0 (fixes < 2.8.0) | — | ghsa |
Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.
Affected Packages
(1 across 1 ecosystem)
Packagist(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| shopper/framework | v2.0.0 ... v2.7.3 (59 versions) |
| — |
Weakness Classification(3)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 10× in last 7d / 41× in last 30d)
Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.
Showing the most recent 100 of 128 refreshes on record for this CVE.
A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 28 oldest rows on record are not shown and were not checked, so the counts can still include repeats.
- 2026-11-01 16:34 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
- 2026-11-01 07:47 UTCGHSA enrichmentGHSA-hr9v-r8r2-hg7j · GitHub severity HIGH · GitHub CVSS 8.7
- 2026-11-01 07:47 UTCEG score recompute
- 2026-10-31 16:32 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
- 2026-10-31 07:15 UTCEG score recompute
- 2026-10-30 16:34 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
- 2026-10-29 16:33 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
- 2026-10-28 16:32 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
- 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
- 2026-10-26 16:31 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
- 2026-10-25 16:33 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
- 2026-10-25 14:24 UTCEG score recompute
- 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.4% · 31st percentile
- 2026-10-24 06:25 UTCEG score recompute
- 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.4% · 31st percentile
- 2026-10-22 16:34 UTCEPSS rescoreEPSS 0.4% · 31st percentile
- 2026-10-21 16:33 UTCEPSS rescoreEPSS 0.4% · 31st percentile
- 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.4% · 31st percentile
- 2026-10-19 16:32 UTCEPSS rescoreEPSS 0.4% · 30th percentile
- 2026-10-18 16:32 UTCEPSS rescoreEPSS 0.4% · 30th percentile
- 2026-10-18 03:35 UTCEG score recompute
- 2026-10-17 16:34 UTCEPSS rescoreEPSS 0.4% · 30th percentile
- 2026-10-17 12:39 UTCEG score recompute
- 2026-10-16 16:42 UTCEPSS rescoreEPSS 0.4% · 30th percentile
- 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.4% · 30th percentile
Show 75 moreShow fewer
- 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.4% · 30th percentile
- 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.4% · 30th percentile
- 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.4% · 30th percentile
- 2026-10-12 16:01 UTCEG score recompute
- 2026-10-11 19:44 UTCEG score recompute
- 2026-10-11 16:59 UTCEG score recompute
- 2026-10-11 14:23 UTCEG score recompute
- 2026-10-11 13:48 UTCEPSS rescoreEPSS 0.4% · 30th percentile
- 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.4% · 30th percentile
- 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.4% · 30th percentile
- 2026-10-08 17:12 UTCEPSS rescoreEPSS 0.4% · 30th percentile
- 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.4% · 30th percentile
- 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.4% · 30th percentile
- 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.4% · 30th percentile
- 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.4% · 30th percentile
- 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.4% · 30th percentile
- 2026-10-03 11:09 UTCOSV refresh
- 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.4% · 30th percentile
- 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.4% · 29th percentile
- 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.4% · 29th percentile
- 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.4% · 29th percentile
- 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.4% · 29th percentile
- 2026-09-26 00:27 UTCEPSS rescoreEPSS 0.4% · 29th percentile
- 2026-09-23 17:53 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
- 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
- 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
- 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
- 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.4% · 31st percentile
- 2026-09-14 05:00 UTCEG score recompute
- 2026-09-13 16:47 UTCEPSS rescoreEPSS 0.4% · 31st percentile
- 2026-09-12 20:36 UTCOSV refresh
- 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.4% · 31st percentile
- 2026-09-10 09:35 UTCEPSS rescoreEPSS 0.4% · 31st percentile
- 2026-09-08 22:00 UTCEPSS rescoreEPSS 0.4% · 31st percentile
- 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.4% · 31st percentile
- 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.4% · 31st percentile
- 2026-09-04 05:06 UTCEPSS rescoreEPSS 0.4% · 31st percentile
- 2026-09-02 14:12 UTCEPSS rescoreEPSS 0.4% · 31st percentile
- 2026-09-01 13:54 UTCEPSS rescoreEPSS 0.4% · 31st percentile
- 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.4% · 31st percentile
- 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.4% · 31st percentile
- 2026-08-28 21:41 UTCEPSS rescoreEPSS 0.4% · 31st percentile
- 2026-08-27 14:25 UTCEPSS rescoreEPSS 0.4% · 31st percentile
- 2026-08-26 14:46 UTCEPSS rescoreEPSS 0.4% · 31st percentile
- 2026-08-25 13:49 UTCEPSS rescoreEPSS 0.4% · 31st percentile
- 2026-08-25 01:49 UTCEG score recompute
- 2026-08-23 12:22 UTCEG score recompute
- 2026-08-23 00:19 UTCEPSS rescoreEPSS 0.4% · 28th percentile
- 2026-08-22 01:56 UTCEG score recompute
- 2026-08-21 23:49 UTCEPSS rescoreEPSS 0.4% · 28th percentile
- 2026-08-20 22:59 UTCEG score recompute
- 2026-08-20 22:55 UTCEPSS rescoreEPSS 0.4% · 28th percentile
- 2026-08-20 09:37 UTCEG score recompute
- 2026-08-19 17:04 UTCEPSS rescoreEPSS 0.4% · 28th percentile
- 2026-08-18 13:48 UTCEPSS rescoreEPSS 0.4% · 28th percentile
- 2026-08-17 13:47 UTCEPSS rescoreEPSS 0.4% · 28th percentile
- 2026-08-16 16:22 UTCEG score recompute
- 2026-08-16 14:56 UTCEPSS rescoreEPSS 0.4% · 28th percentile
- 2026-08-16 03:12 UTCEG score recompute
- 2026-08-16 02:14 UTCEPSS rescoreEPSS 0.4% · 28th percentile
- 2026-08-15 14:02 UTCEG score recompute
- 2026-08-15 01:30 UTCEPSS rescoreEPSS 0.4% · 28th percentile
- 2026-08-13 22:30 UTCEG score recompute
- 2026-08-13 22:00 UTCEPSS rescoreEPSS 0.4% · 28th percentile
- 2026-08-13 02:24 UTCEG score recompute
- 2026-08-12 13:51 UTCEPSS rescoreEPSS 0.4% · 28th percentile
- 2026-08-12 00:03 UTCEG score recompute
- 2026-08-11 10:52 UTCEG score recompute
- 2026-08-11 00:00 UTCEPSS rescoreEPSS 0.4% · 28th percentile
- 2026-08-09 17:27 UTCEG score recompute
- 2026-08-09 13:46 UTCEPSS rescoreEPSS 0.4% · 28th percentile
- 2026-08-09 04:17 UTCEG score recompute
- 2026-08-08 16:37 UTCEPSS rescoreEPSS 0.4% · 28th percentile
- 2026-08-08 01:56 UTCEG score recompute
- 2026-08-06 23:35 UTCEG score recompute
Related CVEs(same product + same CWE)
Same product
10 shownPackagist:shopper/framework
Frequently asked(5)
What is CVE-2026-47743?
When was the CVE record for CVE-2026-47743 published?
Is CVE-2026-47743 actively exploited?
What is the CVSS score of CVE-2026-47743?
How do I remediate CVE-2026-47743?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-47743
Is Your Infrastructure Affected by CVE-2026-47743?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.