CVE-2023-46943
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 · uneditedAn issue was discovered in NPM's package @evershop/evershop before version 1.0.0-rc.8. The HMAC secret used for generating tokens is hardcoded as "secret". A weak HMAC secret poses a risk because attackers can use the predictable secret to create valid JSON Web Tokens (JWTs), allowing them access to important information and actions within the application.
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 confidenceThe @evershop/evershop NPM package versions before 1.0.0-rc.8 use a hardcoded HMAC secret ('secret') for signing JWT tokens. Since this secret is both predictable and publicly known, attackers can forge valid JWTs and impersonate any user or gain administrative access to the application.
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
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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.
-
Check installed @evershop/evershop package versionRun 'npm list @evershop/evershop' in your project directory to see the currently installed versionAffected if The installed version is 1.0.0 or any version before 1.0.0-rc.8
-
Verify JWT authentication is in useInspect your application configuration and code for JWT token generation, validation, or authentication middleware that uses JWT. Look for references to 'jsonwebtoken' library or JWT-related environment variablesAffected if The application uses JWT-based authentication with the @evershop/evershop package
-
Search for hardcoded JWT secret in source codeSearch your codebase for the string 'secret' used as an HMAC key for JWT signing. Check files related to JWT configuration, authentication modules, or any hardcoded secret valuesAffected if A hardcoded secret value of 'secret' is found being used for JWT token signing
You are affected if you are running @evershop/evershop version 1.0.0 (or any version before 1.0.0-rc.8) and your application uses JWT authentication with the hardcoded secret.
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 to version 1.0.0-rc.8 or later and replace the hardcoded secret with a strong, unique HMAC secret stored securely in environment variables. Existing user sessions should be invalidated after applying the fix.
1.0.0-rc.8
- 1. Update the @evershop/evershop NPM package to version 1.0.0-rc.8 or later
- 2. Run 'npm update @evershop/evershop' or 'npm install @evershop/[email protected]' in your project directory
- 3. After updating, verify the application functions correctly and test JWT authentication
- 4. Ensure any deployment pipelines also pull the updated version
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-46943 — 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-46943 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