CVE-2026-62990

HIGHPre-NVD 8.78.7
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This high-severity CVE scores 8.7 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2% (15th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
Elevated

Also known asEUVD-2026-114511 (ENISA EUVD)Source: ENISA EUVD

8.7EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 8.7Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

Shopper is a Headless e-commerce Admin Panel. In versions from 2.0.0 prior to 2.10.1 and in the 3.0.0 prereleases beta.1 and beta.2, authenticated back-office staff with a content-upload permission can store executable media on the administrator's own origin. In the 2.x implementation, relevant upload permissions include edit_products or add_brands, and packages/admin/config/media.php allows image/svg+xml in every media collection, including image fields whose image/* validation also accepts SVG. The product files collection in packages/admin/src/Livewire/Components/Products/Form/Files.php has no MIME restriction and accepts text/html as well. Media is served inline from the public disk under /storage/ with its own content type, without Content-Disposition: attachment or a Content-Security-Policy. When an administrator opens an uploaded HTML or SVG file, stored script executes in that administrator's session. In 2.x, the script can invoke packages/admin/src/Livewire/SlideOvers/CreateTeamMember.php, whose store() checks access_setting held by the viewing administrator but trusts client-supplied role_id, to create a new attacker-controlled administrator with a chosen password. This account persists after the uploaded file is deleted and gives access to customer data, orders, settings, and user/role management; the same script can exfiltrate data or grant permissions to the attacker's account. Direct account creation by the low-privileged uploader is blocked, so exploitation requires the administrator to open the file. The 3.x prerelease line already excludes SVG but still allows executable product files. This issue is fixed in versions 2.10.1 and 3.0.0-beta.3.

CVSS v3
8.7
EG Score
8.7HIGHmedium confidence
EG Risk
55
EG Risk 55/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.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track* at medium and Attend at high mission impact.
Exploitation public PoC (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 at low or medium mission impact and sooner than that at high.
EPSS PROB
0.2%
EPSS %ILE
15th
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.a secondary CVSS source · CVSS v3.0 or v3.1
EG Likelihood
0.2% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-11). 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, Track* at medium and Attend at high mission impact.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, Track* at medium and Attend at high mission impact.

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (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

October 30, 2026

Last Modified

November 5, 2026

Advisory Details (8)

Auto-updated Oct 30, 2026
🔬 Proof of concept available. Patch available. Sources: github_commit, github_pr, github_release, github.
GitHub advisoryMentions a patch (unverified)🟡 PoC Available

Stored XSS via unrestricted media/file upload, leading to privilege escalation to administrator · Advisory · shopperlabs/shopper · GitHub

https://github.com/shopperlabs/shopper/security/advisories/GHSA-vmvv-x5cp-2qv6
GitHub release Patch Available

v3.0.0-beta.3

Patch available: shopperlabs/shopper v3.0.0-beta.3 (pre-release)

https://github.com/shopperlabs/shopper/releases/tag/v3.0.0-beta.3
GitHub release Patch Available

v2.10.1: Media Upload and Customer Access Security

Patch available: shopperlabs/shopper v2.10.1

https://github.com/shopperlabs/shopper/releases/tag/v2.10.1
GitHub pull request Patch Available

fix(security): restrict the product files media collection

Patch available: shopperlabs/shopper v3.0.0-beta.3 (PR #597 merged 2026-06-29)

https://github.com/shopperlabs/shopper/pull/597
GitHub pull request Patch Available

fix(security): block executable uploads in media collections

Patch available: shopperlabs/shopper v2.10.1 (PR #595 merged 2026-06-29)

https://github.com/shopperlabs/shopper/pull/595
Web page

Comparing v3.0.0-beta.1...v3.0.0-beta.3 · shopperlabs/shopper · GitHub

https://github.com/shopperlabs/shopper/compare/v3.0.0-beta.1...v3.0.0-beta.3
GitHub commit Patch Available

commit ad2c5b9b968f (shopperlabs/shopper)

Patch available: shopperlabs/shopper v3.0.0-beta.3 (contains commit ad2c5b9b968f)

https://github.com/shopperlabs/shopper/commit/ad2c5b9b968ff49c37130c6b9d1dba7f20eebbf6
GitHub commit Patch Available

commit 12be681db5f6 (shopperlabs/shopper)

Patch available: shopperlabs/shopper v2.10.1 (contains commit 12be681db5f6)

https://github.com/shopperlabs/shopper/commit/12be681db5f603a364d5f03f1974ff2a20e99b99

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 7× in last 7d / 15× 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 its CVE.org record (CNA or CISA ADP). 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). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

  1. 2026-11-12 16:34 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  2. 2026-11-12 12:11 UTCEchelonGraph re-scored
  3. 2026-11-11 16:40 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  4. 2026-11-10 16:45 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  5. 2026-11-09 16:35 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  6. 2026-11-08 16:40 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  7. 2026-11-07 16:39 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  8. 2026-11-06 16:39 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  9. 2026-11-05 16:38 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  10. 2026-11-05 03:26 UTCEchelonGraph re-scored
  11. 2026-11-05 02:59 UTCEchelonGraph re-scored
  12. 2026-11-04 16:36 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  13. 2026-11-03 16:48 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  14. 2026-11-02 16:45 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  15. 2026-11-01 16:35 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  16. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  17. 2026-10-30 23:02 UTCENISA EUVD ID recordedEUVD-2026-114511 · Source: ENISA EUVD
  18. 2026-10-30 21:26 UTCEchelonGraph re-scored
  19. 2026-10-30 21:14 UTCEchelonGraph re-scoredFirst assessed: 8.7 HIGH
  20. 2026-10-30 21:13 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-62990?
CVE-2026-62990 is a high-severity vulnerability; its CVE record was published on October 30, 2026. Shopper is a Headless e-commerce Admin Panel. In versions from 2.0.0 prior to 2.10.1 and in the 3.0.0 prereleases beta.1 and beta.2, authenticated back-office staff with a content-upload permission can store executable media on the administrator's own origin. In the 2.x implementation, relevant…
When was the CVE record for CVE-2026-62990 published?
The CVE record for CVE-2026-62990 was published on October 30, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of November 5, 2026; the record at its source may have been updated since.
Is CVE-2026-62990 actively exploited?
CVE-2026-62990 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (15th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-62990?
CVE-2026-62990 has a CVSS base score of 8.7 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-62990?
A fix for CVE-2026-62990 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-62990

Explore →

Is Your Infrastructure Affected by CVE-2026-62990?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs