EvershopApplication

CVE-2023-46495

MEDIUM · 6.1 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 →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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
Cross Site Scripting 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 sortBy parameter.

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

A reflected Cross Site Scripting (XSS) vulnerability exists in the sortBy parameter of EverShop e-commerce platform versions prior to v1.0.0-rc-8. An unauthenticated remote attacker can inject malicious JavaScript code through the crafted sortBy parameter in an HTTP request, which gets reflected back in the response without proper sanitization, potentially allowing session hijacking or sensitive data exfiltration.

MitigationUpgrade EverShop to version 1.0.0-rc-8 or later which contains the security fix for this XSS 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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/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. Confirm EverShop installation
    Identify whether the EverShop e-commerce platform is deployed in your environment. Check for EverShop-specific directories, configurations, or running processes.
    Affected if EverShop is present in the environment
  2. Check installed EverShop version
    Locate the version file or package.json in your EverShop installation. Run: npm list evershop or check package.json version field. Compare against affected range: versions prior to v1.0.0-rc-8 (specifically 1.0.0).
    Affected if Installed version is 1.0.0 or any version prior to 1.0.0-rc-8
  3. Verify sortBy parameter is accessible
    Determine if product listing or catalog pages using the sortBy parameter are accessible on your site. This parameter typically appears on category/product listing pages with sorting options.
    Affected if SortBy parameter functionality is enabled and accessible on storefront pages
  4. Test sortBy parameter for XSS reflection
    Send a crafted HTTP request with a test XSS payload in the sortBy parameter, such as: ?sortBy=<script>alert(1)</script> and observe if the payload is reflected unescaped in the response HTML.
    Affected if The sortBy parameter reflects input without proper encoding or sanitization in the HTTP response

Your environment is affected if EverShop version 1.0.0 or any version prior to 1.0.0-rc-8 is installed AND the sortBy parameter on product listing pages reflects unsanitized input in responses.

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 1.0.0-rc-8 or later which contains the security fix for this XSS vulnerability.

Recommended fix High confidence

v.1.0.0-rc.8 or later

  1. Check the current EverShop version in package.json
  2. Update the EverShop dependency to version 1.0.0-rc.8 or later by running: npm install @evershop/[email protected] (or latest stable version)
  3. Run npm install to update all dependencies
  4. Test the application to verify the sortBy parameter is properly sanitized

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

Fix this in Evershop Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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