dbcve.org
EvershopApplication

CVE-2023-46498

CRITICAL · 9.8 CVSS v3.1 Published 2023-12-08
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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
An issue in EverShop NPM versions before v.1.0.0-rc.8 allows a remote attacker to obtain sensitive information and execute arbitrary code via the /deleteCustomer/route.json file.

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 · moderate confidence

EverShop e-commerce platform versions before v1.0.0-rc.8 contain a critical vulnerability in the /deleteCustomer/route.json endpoint that allows unauthenticated remote attackers to both disclose sensitive information and execute arbitrary code, likely through command or code injection.

MitigationUpgrade EverShop to v1.0.0-rc.8 or later; if immediate upgrade is not feasible, disable or restrict access to the /deleteCustomer endpoint at the web server or network level as a compensating control.

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:= 1.0.0

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. Identify EverShop installation location
    Locate the EverShop installation directory. Common paths include /var/www/evershop, /opt/evershop, or the web root directory. Look for the package.json file which contains version metadata.
    Affected if EverShop is installed and the version is 1.0.0 or any version before v1.0.0-rc.8
  2. Determine installed EverShop version
    Read the package.json file in the EverShop root directory. Look for the 'version' field. Alternatively, run 'npm list evershop' if npm is available in the installation directory.
    Affected if The installed version is 1.0.0 or any version lower than 1.0.0-rc.8
  3. Verify the /deleteCustomer endpoint exists
    Check for the file routes/deleteCustomer/route.json within the EverShop installation directory. This file should exist in unpatched versions.
    Affected if The file routes/deleteCustomer/route.json exists in the installation
  4. Test endpoint accessibility
    Send a GET or POST request to the /deleteCustomer endpoint on the running server. For example: curl -k https://targetsite.com/deleteCustomer or check if the route is loaded by the application.
    Affected if The endpoint responds to requests, indicating it is exposed and potentially exploitable
  5. Inspect for signs of compromise
    Review web server access logs and application logs for requests to /deleteCustomer from unexpected IP addresses. Check for suspicious command execution patterns or unexpected file modifications in the EverShop directory.
    Affected if Log entries show unauthorized access to /deleteCustomer or unexpected system command execution

A user is affected if EverShop version 1.0.0 or any version before v1.0.0-rc.8 is installed and the /deleteCustomer endpoint is exposed and accessible without authentication.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade EverShop to v1.0.0-rc.8 or later; if immediate upgrade is not feasible, disable or restrict access to the /deleteCustomer endpoint at the web server or network level as a compensating control.

Recommended fix High confidence

v.1.0.0-rc.8 or later

  1. 1. Backup your current EverShop installation and database before upgrading
  2. 2. Navigate to your EverShop project directory
  3. 3. Check your current package.json to identify the current EverShop version
  4. 4. Run 'npm install [email protected]' or 'npm update evershop' to upgrade to the fixed version
  5. 5. Verify the installation completed successfully
  6. 6. Test your application to ensure normal functionality after the upgrade
  7. 7. Ensure any custom code or themes are compatible with the new version

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

Fix this in Evershop Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-46498 — 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-2023-46498 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