CVE-2026-72843: evershopcommerce evershop · Missing Authorization
Affects evershopcommerce evershopSource CVE Database V5
Not known to be exploited · CVSS 9.3 Critical : upgrade to 2.2.1 as a priority.
Data as of 18 Nov 2026, 20:25 UTC
- EPSS
- 0.8% chance of exploitation in 30 days – higher than 58% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 2.2.1
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 20 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 18 Nov 2026.
What to do
Upgrade evershopcommerce evershop to 2.2.1.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| evershopcommerceevershop | Affected
| Fixed in
|
GitHubevershoppkg:github/evershopOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade to EverShop version 2.2.1 or later, where the customer update route access is changed to "private" to enforce proper authorization. Until upgrade, restrict access to the customer update API route to trusted users only. Patch status is confirmed fixed in version 2.2.1.
Description
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".
References
- github.com/evershopcommerce/evershop/issues/952 (opens in a new tab)
- github.com/evershopcommerce/evershop/blob/v2.1.2/packages/evershop/src/modules/customer/api/updateCustomer/route.json (opens in a new tab)
- github.com/evershopcommerce/evershop/blob/v2.1.2/packages/evershop/src/modules/customer/api/updateCustomer/updateCustomer.js (opens in a new tab)
- github.com/evershopcommerce/evershop/releases/tag/v2.2.1 (opens in a new tab)
- github.com/evershopcommerce/evershop (opens in a new tab)
- vulncheck.com/advisories/evershop-missing-authorization-on-patch-api-customers-id-allows-unauthenticated-account-takeover (opens in a new tab)