dbcve.org
EvershopApplication

CVE-2023-46493

MEDIUM · 5.3 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 →
62/100
Remediation priority · Elevated
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
Directory Traversal vulnerability in EverShop NPM versions before v.1.0.0-rc.8 allows a remote attacker to obtain sensitive information via a crafted request to the readDirSync function in fileBrowser/browser.js.

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

Directory traversal vulnerability in EverShop's fileBrowser/browser.js allows remote attackers to access sensitive files via path traversal sequences (e.g., ../) in requests to the readDirSync function, enabling unauthorized file system access and information disclosure.

MitigationUpgrade to EverShop v1.0.0-rc.8 or later, which contains the patch for this vulnerability.

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
Low
Integrity
None
Availability
None

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

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 and version
    Check package.json in the EverShop root directory for the 'version' field, or run 'npm list evershop' if npm is available
    Affected if Version is 1.0.0 (exact match to affected version)
  2. Locate the vulnerable fileBrowser module
    Check for the existence of fileBrowser/browser.js in the application source tree, typically under node_modules or the src directory
    Affected if The file fileBrowser/browser.js exists and contains the readDirSync function
  3. Verify the readDirSync function is exposed
    Examine the application's routes or API endpoints that invoke the fileBrowser module's readDirSync function - look for references to 'fileBrowser' or 'browser.js' in route definitions
    Affected if The readDirSync function is exposed via an HTTP-accessible endpoint without authentication checks
  4. Test for path traversal vulnerability
    Send an HTTP GET request to the fileBrowser endpoint with a path traversal payload such as '../../../etc/passwd' or '../../../config' - check if the response contains file contents outside the intended directory
    Affected if The application returns file contents from directories outside the intended fileBrowser root directory

The environment is affected if running EverShop version 1.0.0 with the fileBrowser/browser.js module exposed and accessible, and path traversal sequences return unauthorized file contents.

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 to EverShop v1.0.0-rc.8 or later, which contains the patch for this vulnerability.

Recommended fix Moderate confidence

v.1.0.0-rc.8 or later (upgrade to latest stable release)

  1. 1. Identify the current EverShop installation version by checking package.json or the installed npm package.
  2. 2. Verify the exact version currently in use by running `npm list evershop` or checking `node_modules/evershop/package.json`.
  3. 3. If the installed version is before v.1.0.0-rc.8, upgrade to v.1.0.0-rc.8 or a later stable release.
  4. 4. Run `npm install [email protected]` or `npm install evershop@latest` to apply the security fix.
  5. 5. After upgrading, restart the EverShop application services.
  6. 6. Test the fileBrowser functionality to ensure the application still works correctly after the upgrade.
  7. 7. Verify the vulnerability is remediated by attempting a path traversal request (e.g., `../../` in fileBrowser endpoints) - this should now be blocked.

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
  • Testing2.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,780
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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