Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

Back
New CVE Detected

CVE-2026-72843 – Unauthenticated Account Takeover – EverShop < 2.2.1

Be the first to know when new zero-days emerge:

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-72843 is a critical Missing Authorization vulnerability (CWE-862) in EverShop, an open-source e-commerce platform. The customer update API endpoint is configured for public access, allowing any unauthenticated attacker who knows a customer’s UUID to overwrite that customer’s email address and password and fully take over the account. The flaw carries a CVSS score of 9.3 (CVSS v4.0) / 9.8 (CVSS v3.1), reflecting network-exploitable, no-privilege, no-interaction account compromise.

Technical details

  • Root cause: the customer update route (PATCH /api/customers/:id) is declared with "access": "public" in its route configuration, so the admin authentication middleware calls next() without verifying caller identity.
  • No customer-session middleware is applied to the handler to confirm the requester owns the account being modified.
  • Trigger condition: an attacker only needs to know or guess a target customer’s UUID; no authentication token or session is required.
  • Attack vector: network, sent directly to the exposed API endpoint (packages/evershop/src/modules/customer/api/updateCustomer).
  • Impact: full account takeover — attacker can change the victim’s email and password, locking out the legitimate owner and gaining control of order history, saved payment/shipping details, and any stored personal data.

Affected software

  • EverShop (npm package @evershop/evershop) — all versions prior to 2.2.1

Severity

  • CVSS v3.1: 9.8 (CRITICAL) — CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
  • CVSS v4.0: 9.3 (CRITICAL) — CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Mitigation and recommended actions

  • Immediate: upgrade EverShop to version 2.2.1 or later, which changes the customer update route’s access configuration from "access": "public" to "access": "private", restoring authentication and authorization checks.
  • If immediate patching is not possible: place the affected endpoint behind a reverse proxy or WAF rule that blocks unauthenticated PATCH requests to /api/customers/*, and monitor logs for anomalous unauthenticated update requests targeting customer records.
  • After patching, consider rotating credentials/sessions for customer accounts that may have been targeted prior to remediation.

How IONIX identifies potentially affected assets

IONIX matches the following signals against data already collected when it crawled the asset; identifying the technology sends no request beyond that crawl.

  • Raw response body: class="frontStore", /assets/frontstore-vendor/client/

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge