CVE-2026-72843

CRITICALPre-NVD 9.89.8
EchelonGraph scoreMEDIUM confidence

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

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2026-08-21. A secondary CVSS source baseline 9.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source

Also known asEUVD-2026-63730 (ENISA EUVD) · GHSA-m3qj-pp48-6w2p (GitHub Security Advisories)Source: ENISA EUVD

9.8EG
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).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.8%CVSS: 9.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

The customer update route in EverShop is declared with "access": "public" in packages/evershop/src/modules/customer/api/updateCustomer/route.json, which causes the admin authentication middleware to call next() without checking the caller, and no customer-session middleware guards the route; the only middleware in the chain parses the JSON body. The handler in updateCustomer.js then loads the customer by the uuid taken from the URL path and writes the supplied fields back to that record, hashing a password if one is provided, without verifying that the caller owns the record. An unauthenticated request carrying a known customer uuid can therefore overwrite that customer's email address and password and read back the updated record from the 200 response, taking over the account and locking out its owner. Customer uuids are exposed through order confirmation email links and administrative URLs. Version 2.2.1 changes the route to "access": "private".

CVSS v3
9.8
EG Score
9.8CRITICALmedium confidence
EG Risk
59
EG Risk 59/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)
Severity98% × 45%
Impact severity (EG Severity): CVSS 9.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.8% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (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.8%
EPSS %ILE
58th
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 (9.8): severity, escalated by confirmed exploitation. This CVE's 9.8 is its impact severity (EG Severity), not escalated.

EG Severity
9.8 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.8% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-21). 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; Attend at high (mission-essential systems).CISA BOD 26-04: 3 days if the affected system is publicly exposed; 60 days 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; Attend at high (mission-essential systems).

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

Exploitation none (CISA Vulnrichment) · Automatable yes (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)3 days if the affected system is publicly exposed; 60 days if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (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

August 20, 2026

Last Modified

October 18, 2026

Advisory Details (6)

Auto-updated Nov 15, 2026
Patch available. Sources: github_release.
Web page

EverShop Missing Authorization on PATCH /api/customers/:id Allows Unauthenticated Account Takeover | Advisories | VulnCheck

https://www.vulncheck.com/advisories/evershop-missing-authorization-on-patch-api-customers-id-allows-unauthenticated-account-takeover
GitHub release Patch Available

v2.2.1

Patch available: evershopcommerce/evershop v2.2.1

https://github.com/evershopcommerce/evershop/releases/tag/v2.2.1
Web page

[BUG] Unauthenticated Account Takeover via Missing Authorization on Customer Update Endpoint · Issue #952 · evershopcommerce/evershop · GitHub

https://github.com/evershopcommerce/evershop/issues/952
Web page

evershop/packages/evershop/src/modules/customer/api/updateCustomer/updateCustomer.js at v2.1.2 · evershopcommerce/evershop · GitHub

https://github.com/evershopcommerce/evershop/blob/v2.1.2/packages/evershop/src/modules/customer/api/updateCustomer/updateCustomer.js
Web page

evershop/packages/evershop/src/modules/customer/api/updateCustomer/route.json at v2.1.2 · evershopcommerce/evershop · GitHub

https://github.com/evershopcommerce/evershop/blob/v2.1.2/packages/evershop/src/modules/customer/api/updateCustomer/route.json
Web page

GitHub - evershopcommerce/evershop: 🛍️ Typescript E-commerce Platform · GitHub

https://github.com/evershopcommerce/evershop

Vendor Advisories for CVE-2026-72843(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 13× in last 7d / 59× 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.

Showing the most recent 100 of 466 rows 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 366 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-21 21:43 UTCEchelonGraph re-scored
  2. 2026-11-21 21:43 UTCGHSA enrichmentGHSA-m3qj-pp48-6w2p · GitHub severity CRITICAL · GitHub CVSS 9.8
  3. 2026-11-21 16:41 UTCEPSS rescoreEPSS 0.8% · 58th percentile
  4. 2026-11-20 21:30 UTCEchelonGraph re-scored
  5. 2026-11-20 21:30 UTCGHSA enrichmentGHSA-m3qj-pp48-6w2p · GitHub severity CRITICAL · GitHub CVSS 9.8
  6. 2026-11-20 16:38 UTCEPSS rescoreEPSS 0.8% · 58th percentile
  7. 2026-11-19 21:17 UTCEchelonGraph re-scored
  8. 2026-11-19 21:17 UTCGHSA enrichmentGHSA-m3qj-pp48-6w2p · GitHub severity CRITICAL · GitHub CVSS 9.8
  9. 2026-11-19 16:35 UTCEPSS rescoreEPSS 0.8% · 58th percentile
  10. 2026-11-18 21:05 UTCEchelonGraph re-scored
  11. 2026-11-18 21:05 UTCGHSA enrichmentGHSA-m3qj-pp48-6w2p · GitHub severity CRITICAL · GitHub CVSS 9.8
  12. 2026-11-18 16:35 UTCEPSS rescoreEPSS 0.8% · 58th percentile
  13. 2026-11-17 20:51 UTCEchelonGraph re-scored
  14. 2026-11-17 20:51 UTCGHSA enrichmentGHSA-m3qj-pp48-6w2p · GitHub severity CRITICAL · GitHub CVSS 9.8
  15. 2026-11-17 16:36 UTCEPSS rescoreEPSS 0.8% · 58th percentile
  16. 2026-11-16 20:36 UTCEchelonGraph re-scored
  17. 2026-11-16 20:36 UTCGHSA enrichmentGHSA-m3qj-pp48-6w2p · GitHub severity CRITICAL · GitHub CVSS 9.8
  18. 2026-11-16 16:52 UTCEPSS rescoreEPSS 0.8% · 58th percentile
  19. 2026-11-15 20:23 UTCEchelonGraph re-scored
  20. 2026-11-15 20:23 UTCGHSA enrichmentGHSA-m3qj-pp48-6w2p · GitHub severity CRITICAL · GitHub CVSS 9.8
  21. 2026-11-15 17:02 UTCEPSS rescoreEPSS 0.8% · 58th percentile
  22. 2026-11-14 20:07 UTCEchelonGraph re-scored
  23. 2026-11-14 20:07 UTCGHSA enrichmentGHSA-m3qj-pp48-6w2p · GitHub severity CRITICAL · GitHub CVSS 9.8
  24. 2026-11-14 16:41 UTCEPSS rescoreEPSS 0.8% · 58th percentile
  25. 2026-11-13 19:52 UTCEchelonGraph re-scored
Show 75 more
  1. 2026-11-13 19:52 UTCGHSA enrichmentGHSA-m3qj-pp48-6w2p · GitHub severity CRITICAL · GitHub CVSS 9.8
  2. 2026-11-13 16:57 UTCEPSS rescoreEPSS 0.8% · 58th percentile
  3. 2026-11-12 18:19 UTCEchelonGraph re-scored
  4. 2026-11-12 18:19 UTCGHSA enrichmentGHSA-m3qj-pp48-6w2p · GitHub severity CRITICAL · GitHub CVSS 9.8
  5. 2026-11-12 16:34 UTCEPSS rescoreEPSS 0.8% · 58th percentile
  6. 2026-11-11 18:04 UTCEchelonGraph re-scored
  7. 2026-11-11 18:04 UTCGHSA enrichmentGHSA-m3qj-pp48-6w2p · GitHub severity CRITICAL · GitHub CVSS 9.8
  8. 2026-11-11 16:40 UTCEPSS rescoreEPSS 0.8% · 58th percentile
  9. 2026-11-10 17:51 UTCEchelonGraph re-scored
  10. 2026-11-10 17:51 UTCGHSA enrichmentGHSA-m3qj-pp48-6w2p · GitHub severity CRITICAL · GitHub CVSS 9.8
  11. 2026-11-10 16:45 UTCEPSS rescoreEPSS 0.8% · 58th percentile
  12. 2026-11-09 17:37 UTCEchelonGraph re-scored
  13. 2026-11-09 17:37 UTCGHSA enrichmentGHSA-m3qj-pp48-6w2p · GitHub severity CRITICAL · GitHub CVSS 9.8
  14. 2026-11-09 16:36 UTCEPSS rescoreEPSS 0.8% · 58th percentile
  15. 2026-11-08 17:24 UTCEchelonGraph re-scored
  16. 2026-11-08 17:24 UTCGHSA enrichmentGHSA-m3qj-pp48-6w2p · GitHub severity CRITICAL · GitHub CVSS 9.8
  17. 2026-11-08 16:40 UTCEPSS rescoreEPSS 0.8% · 57th percentile
  18. 2026-11-07 17:12 UTCEchelonGraph re-scored
  19. 2026-11-07 17:12 UTCGHSA enrichmentGHSA-m3qj-pp48-6w2p · GitHub severity CRITICAL · GitHub CVSS 9.8
  20. 2026-11-07 16:39 UTCEPSS rescoreEPSS 0.8% · 57th percentile
  21. 2026-11-06 16:59 UTCEchelonGraph re-scored
  22. 2026-11-06 16:59 UTCGHSA enrichmentGHSA-m3qj-pp48-6w2p · GitHub severity CRITICAL · GitHub CVSS 9.8
  23. 2026-11-06 16:55 UTCOSV refresh
  24. 2026-11-06 16:39 UTCEPSS rescoreEPSS 0.8% · 57th percentile
  25. 2026-11-05 16:46 UTCEchelonGraph re-scored
  26. 2026-11-05 16:46 UTCGHSA enrichmentGHSA-m3qj-pp48-6w2p · GitHub severity CRITICAL · GitHub CVSS 9.8
  27. 2026-11-05 16:38 UTCEPSS rescoreEPSS 0.8% · 57th percentile
  28. 2026-11-04 16:36 UTCEPSS rescoreEPSS 0.8% · 57th percentile
  29. 2026-11-04 16:33 UTCEchelonGraph re-scored
  30. 2026-11-04 16:33 UTCGHSA enrichmentGHSA-m3qj-pp48-6w2p · GitHub severity CRITICAL · GitHub CVSS 9.8
  31. 2026-11-03 16:49 UTCEPSS rescoreEPSS 0.8% · 57th percentile
  32. 2026-11-03 16:20 UTCEchelonGraph re-scored
  33. 2026-11-03 16:20 UTCGHSA enrichmentGHSA-m3qj-pp48-6w2p · GitHub severity CRITICAL · GitHub CVSS 9.8
  34. 2026-11-02 16:46 UTCEPSS rescoreEPSS 0.8% · 57th percentile
  35. 2026-11-02 15:59 UTCEchelonGraph re-scored
  36. 2026-11-02 15:59 UTCGHSA enrichmentGHSA-m3qj-pp48-6w2p · GitHub severity CRITICAL · GitHub CVSS 9.8
  37. 2026-11-01 16:35 UTCEPSS rescoreEPSS 0.8% · 57th percentile
  38. 2026-11-01 15:46 UTCEchelonGraph re-scored
  39. 2026-11-01 15:46 UTCGHSA enrichmentGHSA-m3qj-pp48-6w2p · GitHub severity CRITICAL · GitHub CVSS 9.8
  40. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.8% · 57th percentile
  41. 2026-10-31 15:33 UTCEchelonGraph re-scored
  42. 2026-10-31 15:33 UTCGHSA enrichmentGHSA-m3qj-pp48-6w2p · GitHub severity CRITICAL · GitHub CVSS 9.8
  43. 2026-10-30 16:35 UTCEPSS rescoreEPSS 0.8% · 57th percentile
  44. 2026-10-30 15:21 UTCEchelonGraph re-scored
  45. 2026-10-30 15:21 UTCGHSA enrichmentGHSA-m3qj-pp48-6w2p · GitHub severity CRITICAL · GitHub CVSS 9.8
  46. 2026-10-29 16:34 UTCEPSS rescoreEPSS 0.8% · 57th percentile
  47. 2026-10-29 15:09 UTCEchelonGraph re-scored
  48. 2026-10-29 15:09 UTCGHSA enrichmentGHSA-m3qj-pp48-6w2p · GitHub severity CRITICAL · GitHub CVSS 9.8
  49. 2026-10-28 16:33 UTCEPSS rescoreEPSS 0.8% · 57th percentile
  50. 2026-10-28 14:56 UTCEchelonGraph re-scored
  51. 2026-10-28 14:56 UTCGHSA enrichmentGHSA-m3qj-pp48-6w2p · GitHub severity CRITICAL · GitHub CVSS 9.8
  52. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.8% · 57th percentile
  53. 2026-10-27 14:19 UTCEchelonGraph re-scored
  54. 2026-10-27 14:19 UTCGHSA enrichmentGHSA-m3qj-pp48-6w2p · GitHub severity CRITICAL · GitHub CVSS 9.8
  55. 2026-10-26 16:32 UTCEPSS rescoreEPSS 0.8% · 57th percentile
  56. 2026-10-26 13:47 UTCEchelonGraph re-scored
  57. 2026-10-26 13:46 UTCGHSA enrichmentGHSA-m3qj-pp48-6w2p · GitHub severity CRITICAL · GitHub CVSS 9.8
  58. 2026-10-25 16:33 UTCEPSS rescoreEPSS 0.8% · 57th percentile
  59. 2026-10-25 14:06 UTCEchelonGraph re-scored
  60. 2026-10-25 13:13 UTCEchelonGraph re-scored
  61. 2026-10-25 13:13 UTCGHSA enrichmentGHSA-m3qj-pp48-6w2p · GitHub severity CRITICAL · GitHub CVSS 9.8
  62. 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.8% · 57th percentile
  63. 2026-10-24 13:00 UTCEchelonGraph re-scored
  64. 2026-10-24 13:00 UTCGHSA enrichmentGHSA-m3qj-pp48-6w2p · GitHub severity CRITICAL · GitHub CVSS 9.8
  65. 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.8% · 57th percentile
  66. 2026-10-23 12:46 UTCEchelonGraph re-scored
  67. 2026-10-23 12:45 UTCGHSA enrichmentGHSA-m3qj-pp48-6w2p · GitHub severity CRITICAL · GitHub CVSS 9.8
  68. 2026-10-22 16:35 UTCEPSS rescoreEPSS 0.8% · 57th percentile
  69. 2026-10-22 12:29 UTCEchelonGraph re-scored
  70. 2026-10-22 12:29 UTCGHSA enrichmentGHSA-m3qj-pp48-6w2p · GitHub severity CRITICAL · GitHub CVSS 9.8
  71. 2026-10-21 16:33 UTCEPSS rescoreEPSS 0.8% · 57th percentile
  72. 2026-10-21 12:16 UTCEchelonGraph re-scored
  73. 2026-10-21 12:16 UTCGHSA enrichmentGHSA-m3qj-pp48-6w2p · GitHub severity CRITICAL · GitHub CVSS 9.8
  74. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.8% · 57th percentile
  75. 2026-10-20 12:03 UTCGHSA enrichmentGHSA-m3qj-pp48-6w2p · GitHub severity CRITICAL · GitHub CVSS 9.8

Frequently asked(5)

What is CVE-2026-72843?
CVE-2026-72843 is a critical-severity vulnerability; its CVE record was published on August 20, 2026. The customer update route in EverShop is declared with "access": "public" in packages/evershop/src/modules/customer/api/updateCustomer/route.json, which causes the admin authentication middleware to call next() without checking the caller, and no customer-session middleware guards the route; the…
When was CVE-2026-72843 made public?
CVE-2026-72843 was made public on June 16, 2026: that is the date its CVE record's CNA, VulnCheck, gives for when the vulnerability was made public. The CVE record itself was published on August 20, 2026. EchelonGraph's copy of the record carries a last-modified date of October 18, 2026; the record at its source may have been updated since.
Is CVE-2026-72843 actively exploited?
CVE-2026-72843 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.8% probability of exploitation in the next 30 days (58th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-72843?
CVE-2026-72843 has a CVSS base score of 9.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-72843?
A fix for CVE-2026-72843 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-72843 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-72843?

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