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-4668 Amelia <= 2.1.2 - Authenticated (Manager+) SQL Injection via 'sort' Parameter — Booking for Appointments and Events Calendar – Amelia 6.5 Medium2026-03-31
CVE-2026-5237 itsourcecode Payroll Management System Parameter manage_user.php sql injection — Payroll Management System 7.3 High2026-03-31
CVE-2026-34400 alerta-server has potential SQL Injection vulnerability in Query String Syntax (q=) API — alerta 9.8 -2026-03-31
CVE-2026-5206 code-projects Simple Gym Management System Payment sql injection — Simple Gym Management System 6.3 Medium2026-03-31
CVE-2026-34220 MikroORM is vulnerable to SQL Injection via specially crafted object — mikro-orm 9.8AICriticalAI2026-03-31
CVE-2026-5198 code-projects Student Membership System Admin Login index.php sql injection — Student Membership System 7.3 High2026-03-31
CVE-2026-5197 code-projects Student Membership System delete_user.php sql injection — Student Membership System 6.3 Medium2026-03-31
CVE-2026-4317 SQL inyection in Umami Software application — Umami Software 8.8AIHighAI2026-03-31
CVE-2026-5196 code-projects Student Membership System delete_member.php sql injection — Student Membership System 6.3 Medium2026-03-31
CVE-2026-5195 code-projects Student Membership System User Registration sql injection — Student Membership System 7.3 High2026-03-31
CVE-2026-5182 SourceCodester Teacher Record System Parameter sql injection — Teacher Record System 7.3 High2026-03-31
CVE-2026-5180 SourceCodester Simple Doctors Appointment System ajax.php sql injection — Simple Doctors Appointment System 7.3 High2026-03-31
CVE-2026-5179 SourceCodester Simple Doctors Appointment System login.php sql injection — Simple Doctors Appointment System 7.3 High2026-03-31
CVE-2026-32714 SciTokens vulnerable to SQL Injection in KeyCache — scitokens 9.8 Critical2026-03-31
CVE-2026-27697 baserCMS: SQL injection vulnerability in blog post — basercms 9.8AICriticalAI2026-03-31
CVE-2026-5150 code-projects Accounting System Parameter viewin_costumer.php sql injection — Accounting System 7.3 High2026-03-30
CVE-2026-5148 YunaiV yudao-cloud page sql injection — yudao-cloud 4.7 Medium2026-03-30
CVE-2026-31799 Tautulli: SQL Injection in get_home_stats API endpoint via unsanitised filter parameters — Tautulli 4.9 Medium2026-03-30
CVE-2026-5147 YunaiV yudao-cloud get-by-website sql injection — yudao-cloud 7.3 High2026-03-30
CVE-2026-5035 code-projects Accounting System Parameter view_work.php sql injection — Accounting System 7.3 High2026-03-29
CVE-2026-5034 code-projects Accounting System Parameter edit_costumer.php sql injection — Accounting System 7.3 High2026-03-29
CVE-2026-5033 code-projects Accounting System Parameter view_costumer.php sql injection — Accounting System 7.3 High2026-03-29
CVE-2026-5019 code-projects Simple Food Order System Parameter all-orders.php sql injection — Simple Food Order System 7.3 High2026-03-28
CVE-2026-5018 code-projects Simple Food Order System Parameter register-router.php sql injection — Simple Food Order System 7.3 High2026-03-28
CVE-2026-5017 code-projects Simple Food Order System Parameter all-tickets.php sql injection — Simple Food Order System 7.3 High2026-03-28
CVE-2026-4996 Sinaptik AI PandasAI pandasai-lancedb Extension lancedb.py get_relevant_docs_by_id sql injection — PandasAI 7.3 High2026-03-28
CVE-2026-33991 WeGIA has SQL Injection in deletar_tag.php — WeGIA 8.8 High2026-03-27
CVE-2026-34386 Fleet vulnerable to SQL injection in MDM bootstrap package by authenticated team or global admin — fleet 6.5 -2026-03-27
CVE-2026-34385 Fleet's Apple MDM profile delivery has second-order SQL injection that can compromise the database — fleet 8.8 -2026-03-27
CVE-2026-4970 code-projects Social Networking Site Endpoint delete_photos.php sql injection — Social Networking Site 6.3 Medium2026-03-27

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