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

Goal: 1000 CNY · Raised: 1000 CNY

100.0%

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

8951 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-7118 code-projects Employee Management System cancel.php sql injection — Employee Management System 6.3 Medium2026-04-27
CVE-2026-7117 code-projects Employee Management System approve.php sql injection — Employee Management System 6.3 Medium2026-04-27
CVE-2026-7115 code-projects Employee Management System delete.php sql injection — Employee Management System 6.3 Medium2026-04-27
CVE-2026-22336 WordPress Directorist Booking plugin < 3.0.2 - SQL Injection vulnerability — Directorist Booking 9.3 Critical2026-04-27
CVE-2026-7114 code-projects Employee Management System edit.php sql injection — Employee Management System 6.3 Medium2026-04-27
CVE-2026-7088 SourceCodester Pharmacy Sales and Inventory System ajax.php sql injection — Pharmacy Sales and Inventory System 7.3 High2026-04-27
CVE-2026-7087 SourceCodester Pharmacy Sales and Inventory System ajax.php sql injection — Pharmacy Sales and Inventory System 7.3 High2026-04-27
CVE-2026-7083 likeadmin-likeshop likeadmin_php dataTable Admin API DataTableLists.php queryResult sql injection — likeadmin_php 4.7 Medium2026-04-27
CVE-2026-7077 itsourcecode Courier Management System edit_parcel.php sql injection — Courier Management System 7.3 High2026-04-27
CVE-2026-7076 itsourcecode Courier Management System edit_branch.php sql injection — Courier Management System 7.3 High2026-04-27
CVE-2026-7075 itsourcecode Construction Management System locations.php sql injection — Construction Management System 7.3 High2026-04-27
CVE-2026-7074 itsourcecode Construction Management System execute1.php sql injection — Construction Management System 7.3 High2026-04-27
CVE-2026-7073 itsourcecode Construction Management System execute.php sql injection — Construction Management System 7.3 High2026-04-27
CVE-2026-7072 CodePanda Source canteen_management_system login.php sql injection — canteen_management_system 7.3 High2026-04-27
CVE-2026-7070 code-projects Inventory Management System Login sql injection — Inventory Management System 7.3 High2026-04-27
CVE-2026-7063 code-projects Employee Management System Endpoint eprocess.php sql injection — Employee Management System 7.3 High2026-04-26
CVE-2026-7060 liyupi yu-picture MyBatis-Plus PictureServiceImpl.java PageRequest sql injection — yu-picture 7.3 High2026-04-26
CVE-2026-7028 CodeAstro Online Job Portal All Jobs delete-jobs.php sql injection — Online Job Portal 4.7 Medium2026-04-26
CVE-2026-7023 ByteDance coze-studio databaseTool database_impl.go ExecuteSQL sql injection — coze-studio 6.3 Medium2026-04-26
CVE-2026-7002 KLiK SocialMediaWebsite Private Message get_message_ajax.php sql injection — SocialMediaWebsite 7.3 High2026-04-25
CVE-2026-6991 colinhacks Zod CUID Data Type regexes.ts sql injection — Zod 6.3 Medium2026-04-25
CVE-2026-6982 star7th ShowDoc API Page Sort Endpoint PageController.class.PHP sql injection — ShowDoc 6.3 Medium2026-04-25
CVE-2026-6978 JiZhiCMS addcache.html htmlspecialchars_decode sql injection — JiZhiCMS 4.7 Medium2026-04-25
CVE-2026-41478 Saltcorn: SQL Injection via Unparameterized Sync Endpoints (maxLoadedId) — saltcorn 10.0 Critical2026-04-24
CVE-2026-33078 Roxy-WI has SQL Injection in haproxy_section_save Endpoint via Unsanitized server_ip Parameter — roxy-wi 9.8AICriticalAI2026-04-24
CVE-2026-31952 Xibo CMS API has SQL Injection via DataSet Filter Parameter — xibo-cms 7.6 High2026-04-24
CVE-2026-41460 SocialEngine <= 7.8.0 SQL Injection via activity/index/get-memberall — SocialEngine 9.8 Critical2026-04-23
CVE-2026-6887 BorG Technology Corporation|Borg SPM 2007 - SQL Injection — Borg SPM 2007 9.8 Critical2026-04-23
CVE-2026-40529 KANATA CMS ALAYA SQL注入漏洞 — CMS ALAYA 6.5AIMediumAI2026-04-23
CVE-2026-41167 Jellystat has SQL Injection that leads to to Remote Code Execution — Jellystat 9.1 Critical2026-04-22

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