CVE-2026-25993
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 · uneditedEverShop is a TypeScript-first eCommerce platform. During category update and deletion event handling, the application embeds path / request_path values—derived from the url_key stored in the database—into SQL statements via string concatenation and passes them to execute(). As a result, if a malicious string is stored in url_key , subsequent event processing modifies and executes the SQL statement, leading to a second-order SQL injection. Patched from v2.1.1.
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 confidenceEverShop fails to sanitize the url_key field when embedding it into SQL statements during category update and deletion event handling. The application uses string concatenation to build SQL queries with path/request_path values derived from the database's url_key, enabling a second-order SQL injection when malicious input is stored and later executed during event processing.
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<= 2.1.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
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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.
-
Identify EverShop installation and versionCheck package.json in the application root for the 'evershop' package version, or run 'npm list evershop' to see the installed versionAffected if The installed version is Evershop 2.1.0 or lower
-
Verify category module is in useCheck if the categories table exists in the database and contains entries. Look for tables named 'category' or similar in the database schemaAffected if The application uses the category functionality with stored url_key values
-
Inspect category event handlersSearch for event handler files related to category update and deletion. Look in directories like 'src/modules/catalog/events' or similar for files handling 'updateCategory' or 'deleteCategory' eventsAffected if String concatenation is used to build SQL queries with path/request_path values from the database in these event handlers
-
Check url_key data in databaseQuery the database for the category table and examine the url_key column values. Look for unusual patterns that might indicate stored malicious inputAffected if url_key values contain SQL injection payloads that could be executed during event processing
-
Review SQL query construction in event filesLocate the specific files handling category update/delete events and examine how SQL queries are constructed. Look for direct string concatenation using variables derived from url_keyAffected if The code uses string concatenation instead of parameterized queries when embedding url_key-derived values into SQL statements
A user is affected if they are running EverShop version 2.1.0 or lower and have the category module active with any stored url_key values that get processed by event handlers using unsafe SQL concatenation.
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 EverShop v2.1.1 or later. Until then, validate and sanitize url_key inputs before database storage and replace string concatenation with parameterized queries in all event handlers.
v2.1.1 or later
- Upgrade EverShop to version 2.1.1 or later which contains the security fix for the second-order SQL injection vulnerability
- Test the upgrade in a staging environment before deploying to production
- Verify that category update and deletion functionality works correctly after the upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-25993 — 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-2026-25993 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