CVE-2023-46494
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 · uneditedCross Site Scripting vulnerability in EverShop NPM versions before v.1.0.0-rc.5 allows a remote attacker to obtain sensitive information via a crafted request to the ProductGrid function in admin/productGrid/Grid.jsx.
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 confidenceCross Site Scripting (XSS) vulnerability in EverShop's admin interface ProductGrid component (admin/productGrid/Grid.jsx). An attacker can inject malicious scripts through crafted requests to the ProductGrid function, potentially allowing sensitive information disclosure.
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= 1.0.0CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Confirm EverShop installationLocate the EverShop installation by checking for package.json in your project root or looking for the 'evershop' package in node_modules directoryAffected if EverShop is present in the environment
-
Identify installed EverShop versionRun 'npm list evershop' or check the version field in package.jsonAffected if The installed version is exactly 1.0.0 (no patches or release candidates applied)
-
Verify vulnerable component existsCheck if the file admin/productGrid/Grid.jsx exists in your EverShop installation directoryAffected if The Grid.jsx file exists in the admin/productGrid directory
-
Confirm admin interface is accessibleAccess your EverShop admin panel URL (typically /admin) and verify you can reach the ProductGrid functionalityAffected if The admin interface is accessible and the ProductGrid component loads user-supplied data
You are affected if EverShop version 1.0.0 is installed and the admin/productGrid/Grid.jsx component handles unsanitized user input in the ProductGrid feature.
Generated from the published advisory. Verify against your own configuration.
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 · scopedUpgrade EverShop NPM package to v.1.0.0-rc.5 or later. Additionally, implement proper input sanitization and output encoding in the ProductGrid component to prevent XSS attacks.
1.0.0-rc.5 or later
- Check current EverShop version by examining package.json or running npm list evershop
- Upgrade to version 1.0.0-rc.5 or later by running: npm install [email protected] (or npm install evershop@latest)
- After upgrading, clear any cached build artifacts (rm -rf .next or similar)
- Rebuild the application to ensure the patched Grid.jsx component is included
- Verify the upgrade was successful by checking the installed version
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,512.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-46494 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-46494 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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