EvershopApplication

CVE-2023-46497

MEDIUM · 5.4 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 →
60/100
Remediation priority · Elevated
Remotely reachable 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 mkdirSync function in the folderCreate/createFolder.js endpoint.

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

Directory traversal vulnerability in EverShop's folder creation endpoint (folderCreate/createFolder.js) allows remote attackers to manipulate path arguments in the mkdirSync function to access files outside the intended directory, potentially exposing sensitive system information.

MitigationUpgrade EverShop to version v1.0.0-rc.8 or later. If immediate upgrade is not feasible, implement input validation and path sanitization on the createFolder endpoint to block directory traversal sequences (e.g., ../ patterns).

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/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
    Locate the EverShop application directory. Check for package.json file containing 'evershop' in the project root.
    Affected if EverShop version 1.0.0 is installed and the folderCreate endpoint is accessible.
  2. Verify installed EverShop version
    Run 'npm list evershop' or inspect package.json to confirm the exact version number.
    Affected if The installed version is exactly 1.0.0.
  3. Locate vulnerable folder creation endpoint
    Search for the file folderCreate/createFolder.js in the codebase and verify it uses mkdirSync.
    Affected if The file folderCreate/createFolder.js exists and uses mkdirSync without proper path sanitization.
  4. Check if endpoint is accessible
    Review application routing configuration to confirm the folderCreate endpoint is exposed via API.
    Affected if The /folderCreate endpoint is publicly or internally accessible without authentication.
  5. Inspect path handling in createFolder.js
    Examine the createFolder.js file to see if user-supplied path arguments are passed directly to mkdirSync without validation.
    Affected if Path parameters are used in mkdirSync without sanitization to block '../' sequences.

You are affected if you are running EverShop version 1.0.0 with the folderCreate/createFolder.js endpoint accessible and the path argument is passed to mkdirSync without directory traversal protection.

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 version v1.0.0-rc.8 or later. If immediate upgrade is not feasible, implement input validation and path sanitization on the createFolder endpoint to block directory traversal sequences (e.g., ../ patterns).

Recommended fix High confidence

EverShop v.1.0.0-rc.8 or later

  1. Identify the current EverShop version in use
  2. Backup the existing installation and database
  3. Upgrade EverShop to version 1.0.0-rc.8 or later
  4. Verify the upgrade was successful by checking the version number
  5. Test that the /folderCreate/createFolder.js endpoint no longer accepts path traversal sequences

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

Fix this in Evershop Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

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-46497 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