dbcve.org
EvershopApplication

CVE-2026-28213

CRITICAL · 9.8 CVSS v3.1 Published 2026-02-26
Fix available
A fix is available. Upgrade to 2.1.1 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
EverShop is a TypeScript-first eCommerce platform. Versions prior to 2.1.1 have a vulnerability in the "Forgot Password" functionality. When specifying a target email address, the API response returns the password reset token. This allows an attacker to take over the associated account. Version 2.1.1 fixes the issue.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The forgot password API in EverShop versions prior to 2.1.1 returns the password reset token in the API response itself. An attacker can supply a target email address and receive the valid reset token, then use that token to set a new password and take over the account.

MitigationUpgrade EverShop to version 2.1.1 or later, which removes the token from the API response. Additionally, audit for any accounts that may have been compromised during the window of exposure.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
EvershopApplication
Affected:< 2.1.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check installed EverShop version
    Locate the package.json file in the EverShop installation directory and read the 'version' field, or run 'npm list evershop' or 'cat package.json | grep version' from the installation root
    Affected if version is less than 2.1.1 (e.g., 2.1.0, 2.0.0, 1.0.x, etc.)
  2. Identify the forgot password API endpoint
    Common endpoints include /api/auth/forgot-password or /api/customer/forgot-password. Check your application's API routing configuration or server logs for the actual endpoint path
    Affected if the endpoint exists and is accessible without authentication
  3. Test the forgot password API response
    Send a POST request to the forgot password endpoint with a valid email address (e.g., using curl: curl -X POST https://your-site.com/api/auth/forgot-password -H 'Content-Type: application/json' -d '{"email":"[email protected]"}') and examine the JSON response
    Affected if the response body contains a 'token', 'resetToken', 'reset_token', or similar field with a value that could be used to reset a password
  4. Verify token visibility in API logs
    Check application server logs, API access logs, or monitoring tools for the forgot password endpoint. Search for log entries that contain reset token values in plaintext
    Affected if tokens appear in plain text in any logs associated with password reset requests

You are affected if your EverShop version is prior to 2.1.1 AND the forgot password API endpoint returns the reset token directly in its response body.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2.1.1 or later
Fixed in 2.1.1
Interim mitigation

Upgrade EverShop to version 2.1.1 or later, which removes the token from the API response. Additionally, audit for any accounts that may have been compromised during the window of exposure.

Recommended fix High confidence

2.1.1

  1. Backup the current EverShop installation and database
  2. Ensure you have a way to restore if issues occur
  3. Upgrade EverShop to version 2.1.1 using your package manager (e.g., npm install [email protected] or equivalent)
  4. After upgrade, verify the 'Forgot Password' functionality no longer returns the reset token in the API response
  5. Test that password reset emails are sent correctly without exposing tokens

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Evershop Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,328.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-28213 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-28213 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data