CVE-2026-25993
Second-Order SQL Injection in EverShop Category Update Component
Publication date: 2026-02-10
Last updated on: 2026-02-23
Assigner: GitHub, Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| evershop | evershop | to 2.1.0 (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-89 | The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability is a second-order SQL injection in EverShop, a TypeScript-first eCommerce platform. It occurs during category update and deletion event handling, where the application takes path or request_path values derived from the url_key stored in the database and embeds them into SQL statements using string concatenation. If a malicious string is stored in url_key, it modifies the SQL statement during subsequent event processing, leading to the execution of unintended SQL commands.
How can this vulnerability impact me? :
This vulnerability can have severe impacts because it allows an attacker to execute arbitrary SQL commands on the database without any privileges or user interaction. This can lead to unauthorized data access, data modification, or deletion, potentially compromising the integrity and confidentiality of the data stored in the eCommerce platform.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
How can this vulnerability be detected on my network or system? Can you suggest some commands?
I don't know
What immediate steps should I take to mitigate this vulnerability?
The vulnerability is patched from EverShop version 2.1.1. Immediate mitigation should include upgrading the EverShop platform to version 2.1.1 or later to prevent the second-order SQL injection.