Goal Reached Thanks to every supporter — we hit 100%!

Goal: 1000 CNY · Raised: 1000 CNY

100.0%

CWE-89 (SQL命令中使用的特殊元素转义处理不恰当(SQL注入)) — Vulnerability Class 8957

8957 vulnerabilities classified as CWE-89 (SQL命令中使用的特殊元素转义处理不恰当(SQL注入)). AI Chinese analysis included.

CWE-89 represents a critical input validation weakness where software constructs SQL commands using untrusted data without properly sanitizing special characters. Attackers typically exploit this vulnerability by injecting malicious SQL syntax into user-facing inputs, such as login fields or search queries, to manipulate the database’s behavior. This exploitation can lead to unauthorized data access, data modification, or complete system compromise by bypassing authentication or executing arbitrary commands. Developers mitigate this risk by implementing strict input validation and, most effectively, using parameterized queries or prepared statements. These techniques ensure that user input is treated strictly as data rather than executable code, thereby preventing the injection of malicious SQL elements. By separating code logic from data inputs, applications maintain integrity and protect sensitive information from unauthorized manipulation.

MITRE CWE Description
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.
Common Consequences (5)
Confidentiality, Integrity, AvailabilityExecute Unauthorized Code or Commands
Adversaries could execute system commands, typically by changing the SQL statement to redirect output to a file that can then be executed.
ConfidentialityRead Application Data
Since SQL databases generally hold sensitive data, loss of confidentiality is a frequent problem with SQL injection vulnerabilities.
AuthenticationGain Privileges or Assume Identity, Bypass Protection Mechanism
If poor SQL commands are used to check user names and passwords or perform other kinds of authentication, it may be possible to connect to the product as another user with no previous knowledge of the password.
Access ControlBypass Protection Mechanism
If authorization information is held in a SQL database, it may be possible to change this information through the successful exploitation of a SQL injection vulnerability.
IntegrityModify Application Data
Just as it may be possible to read sensitive information, it is also possible to modify or even delete this information with a SQL injection attack.
Mitigations (5)
Architecture and DesignUse a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid [REF-1482]. For example, consider using persistence layers such as Hibernate or Enterprise Java Beans, which can provide significant protection against SQL injection if used properly.
Architecture and DesignIf available, use structured mechanisms that automatically enforce the separation between data and code. These mechanisms may be able to provide the relevant quoting, encoding, and validation automatically, instead of relying on the developer to provide this capability at every point where output is generated. Process SQL queries using prepared statements, parameterized queries, or stored procedur…
Architecture and Design, OperationRun your code using the lowest privileges that are required to accomplish the necessary tasks [REF-76]. If possible, create isolated accounts with limited privileges that are only used for a single task. That way, a successful attack will not immediately give the attacker access to the rest of the software or its environment. For example, database applications rarely need to run as the database ad…
Architecture and DesignFor any security checks that are performed on the client side, ensure that these checks are duplicated on the server side, in order to avoid CWE-602. Attackers can bypass the client-side checks by modifying values after the checks have been performed, or by changing the client to remove the client-side checks entirely. Then, these modified values would be submitted to the server.
ImplementationWhile it is risky to use dynamically-generated query strings, code, or commands that mix control and data together, sometimes it may be unavoidable. Properly quote arguments and escape any special characters within those arguments. The most conservative approach is to escape or filter all characters that do not pass an extremely strict allowlist (such as everything that is not alphanumeric or whit…
Examples (2)
In 2008, a large number of web servers were compromised using the same SQL injection attack string. This single string worked against many different programs. The SQL injection was then used to modify the web sites to serve malicious code.
The following code dynamically constructs and executes a SQL query that searches for items matching a specified name. The query restricts the items displayed to those where owner matches the user name of the currently-authenticated user.
... string userName = ctx.getAuthenticatedUserName(); string query = "SELECT * FROM items WHERE owner = '" + userName + "' AND itemname = '" + ItemName.Text + "'"; sda = new SqlDataAdapter(query, conn); DataTable dt = new DataTable(); sda.Fill(dt); ...
Bad · C#
SELECT * FROM items WHERE owner = <userName> AND itemname = <itemName>;
Informative
CVE IDTitleCVSSSeverityPublished
CVE-2026-34374 AVideo has SQL Injection in Live_schedule::keyExists() via Unparameterized Stream Key — AVideo 9.1 Critical2026-03-27
CVE-2026-4966 itsourcecode Free Hotel Reservation System index.php sql injection — Free Hotel Reservation System 6.3 Medium2026-03-27
CVE-2026-33770 AVideo has SQL Injection in category.php fixCleanTitle() via Unparameterized clean_title and id Variables — AVideo 9.8 -2026-03-27
CVE-2026-33767 AVideo has SQL Injection via Partial Prepared Statement — videos_id Concatenated Directly into Query — AVideo 9.8 -2026-03-27
CVE-2026-4956 Shenzhen Ruiming Technology Streamax Crocus Parameter DevicePrint.do sql injection — Streamax Crocus 7.3 High2026-03-27
CVE-2026-4955 Shenzhen Ruiming Technology Streamax Crocus OperateStatistic.do sql injection — Streamax Crocus 7.3 High2026-03-27
CVE-2026-4954 mingSoft MCMS Web Content List Endpoint ContentAction.java list sql injection — MCMS 6.3 Medium2026-03-27
CVE-2026-33755 Authenticated SQL Injection in Contact/query addressBookIds filter — groupoffice 8.8 High2026-03-27
CVE-2026-24031 Open-Xchange OX Dovecot Pro 安全漏洞 — OX Dovecot Pro 7.7 High2026-03-27
CVE-2026-4910 Shenzhen Ruiming Technology Streamax Crocus Endpoint RemoteFormat.do sql injection — Streamax Crocus 7.3 High2026-03-27
CVE-2026-4908 code-projects Simple Laundry System Parameter modstaffinfo.php sql injection — Simple Laundry System 7.3 High2026-03-27
CVE-2026-33545 MobSF has SQL Injection in its SQLite Database Viewer Utils — Mobile-Security-Framework-MobSF 5.3 Medium2026-03-26
CVE-2026-33531 InvenTree has Path Traversal In Report Templates — InvenTree 4.9 -2026-03-26
CVE-2026-33153 Tandoor Recipes's Unauthenticated Debug Parameter Leaks Full Raw SQL Queries Including Schema, Table Names, and Access Control Logic — recipes 6.5 -2026-03-26
CVE-2026-33505 Ory Keto has a SQL injection via forged pagination tokens — keto 7.2 High2026-03-26
CVE-2026-33504 Ory Hydra has a SQL injection via forged pagination tokens — hydra 7.2 High2026-03-26
CVE-2026-33503 Ory Kratos has a SQL injection via forged pagination tokens — kratos 7.2 High2026-03-26
CVE-2026-33468 Kysely has a MySQL SQL Injection via Insufficient Backslash Escaping in `sql.lit(string)` usage or similar methods that append string literal values into the compiled SQL strings — kysely 8.1 High2026-03-26
CVE-2026-33442 Kysely has a MySQL SQL Injection via Backslash Escape Bypass in non-type-safe usage of JSON path keys. — kysely 8.1 High2026-03-26
CVE-2026-2511 JS Help Desk – AI-Powered Support & Ticketing System <= 3.0.4 - Unauthenticated SQL Injection via 'multiformid' Parameter — JS Help Desk – AI-Powered Support & Ticketing System 7.5 High2026-03-26
CVE-2026-4876 itsourcecode Free Hotel Reservation System index.php sql injection — Free Hotel Reservation System 6.3 Medium2026-03-26
CVE-2018-25209 OpenBiz Cubi Lite 3.0.8 SQL Injection via username Parameter — OpenBiz Cubi Lite 8.2 High2026-03-26
CVE-2018-25208 qdPM 9.1 SQL Injection via filter_by Parameters — qdPM 8.2 High2026-03-26
CVE-2018-25207 Online Quiz Maker 1.0 SQL Injection via catid Parameter — Online Quiz Maker 7.1 High2026-03-26
CVE-2018-25206 KomSeo Cart 1.3 SQL Injection via edit.php — KomSeo Cart 8.2 High2026-03-26
CVE-2018-25205 ASP.NET jVideo Kit 1.0 SQL Injection via query Parameter — ASP.NET jVideo Kit 8.2 High2026-03-26
CVE-2018-25204 Library CMS 1.0 SQL Injection via admin login — Library CMS 8.2 High2026-03-26
CVE-2018-25203 Online Store System CMS 1.0 SQL Injection via clientaccess — Online Store System CMS 8.2 High2026-03-26
CVE-2018-25202 SAT CFDI 3.3 SQL Injection via signIn endpoint — SAT CFDI 8.2 High2026-03-26
CVE-2018-25201 School Management System CMS 1.0 Admin Login SQL Injection — School Management System CMS 7.1 High2026-03-26

Vulnerabilities classified as CWE-89 (SQL命令中使用的特殊元素转义处理不恰当(SQL注入)) represent 8957 CVEs. The CWE taxonomy describes the weakness; review individual CVEs for product-specific impact.