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

Goal: 1000 CNY · Raised: 1359 CNY

100%

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

10995 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, Availability Execute 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.
Confidentiality Read Application Data
Since SQL databases generally hold sensitive data, loss of confidentiality is a frequent problem with SQL injection vulnerabilities.
Authentication Gain 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 Control Bypass 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.
Integrity Modify 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 Design Use 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 Design If 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, Operation Run 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 Design For 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.
Implementation While 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 ID Title CVSS Severity Published
CVE-2026-86172 DefaultFuction CRM delete.php sql injection — CRM 6.3 Medium 2026-09-06
CVE-2026-86171 DefaultFuction CRM delete.php sql injection — CRM 6.3 Medium 2026-09-06
CVE-2026-86170 DefaultFuction CRM edit.php sql injection — CRM 6.3 Medium 2026-09-06
CVE-2026-86168 code-projects Content Management System login.php sql injection — Content Management System 7.3 High 2026-09-06
CVE-2026-86164 itsourcecode Sales and Inventory System trans_view.php sql injection — Sales and Inventory System 6.3 Medium 2026-09-06
CVE-2026-86163 itsourcecode Sales and Inventory System pro_del.php sql injection — Sales and Inventory System 6.3 Medium 2026-09-06
CVE-2026-86162 SourceCodester Online Voting System ajax.php login sql injection — Online Voting System 7.3 High 2026-09-06
CVE-2026-86161 SourceCodester Online Voting System ajax.php delete_category sql injection — Online Voting System 7.3 High 2026-09-06
CVE-2026-86160 SourceCodester Online Voting System ajax.php delete_voting sql injection — Online Voting System 7.3 High 2026-09-06
CVE-2026-86159 SourceCodester Online Voting System ajax.php save_user sql injection — Online Voting System 7.3 High 2026-09-06
CVE-2026-52775 YesWiki Authenticated SQL Injection in ReactionManager — yeswiki 8.8 High 2026-09-04
CVE-2026-52771 YesWiki: Second-Order SQL Injection in Page Delete API via Unescaped Page Tag (`ApiController::deletePage`) — yeswiki 8.3 High 2026-09-04
CVE-2026-52770 Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') in yeswiki/yeswiki — yeswiki 7.5 High 2026-09-04
CVE-2026-52763 YesWiki: SQL injection via the `recentchanges` action `period` argument leading to arbitrary DB read — yeswiki 6.5 Medium 2026-09-04
CVE-2026-85643 code-projects Online Shopping System adduser.php mysqli_query sql injection — Online Shopping System 4.7 Medium 2026-09-04
CVE-2026-53756 Emlog Blind SQL Injection via Authentication Cookie — emlog 4.9 Medium 2026-09-04
CVE-2026-82538 ILIAS Arbitrary SQL Injection via Repository Trash Table Sort Parameter — ILIAS 8.8 High 2026-09-04
CVE-2026-18658 IBM Operational Decision Manager for Aug 2026 - Multiple CVEs addressed — Operational Decision Manager 9.8 Critical 2026-09-04
CVE-2026-85689 llmware 0.4.6 SQL Injection via unescaped filter values — llmware 6.5 Medium 2026-09-04
CVE-2026-52691 Apache Griffin Hive Metastore Module: SQL Injection Vulnerability in Hive Metastore Module — Apache Griffin Hive Metastore Module - - 2026-09-04
CVE-2026-85516 code-projects Vehicle Management System busprofile.php sql injection — Vehicle Management System 7.3 High 2026-09-04
CVE-2026-18198 SQL Injection in TAC Information's GoldenHorn — GOLDENHORN ONEIT 8.8 High 2026-09-04
CVE-2026-85540 Interinfo|DreamMaker - SQL Injection — DreamMaker 8.8 High 2026-09-04
CVE-2026-57777 WordPress WooCommerce plugin < 11.0 - SQL Injection vulnerability — WooCommerce 7.6 High 2026-09-04
CVE-2026-85403 code-projects Doctor Appointment System contactus.php sql injection — Doctor Appointment System 7.3 High 2026-09-04
CVE-2026-85402 code-projects Doctor Appointment System booking.php sql injection — Doctor Appointment System 7.3 High 2026-09-04
CVE-2026-85399 code-projects Hospital Information System PrespController.php getSinglePresp sql injection — Hospital Information System 7.3 High 2026-09-04
CVE-2026-85398 code-projects Hospital Information System viewReq.php viewReq sql injection — Hospital Information System 7.3 High 2026-09-04
CVE-2026-85397 code-projects Hospital Information System addReq.php findBySearch sql injection — Hospital Information System 7.3 High 2026-09-04
CVE-2026-85383 itsourcecode Sales and Inventory System inv_del.php sql injection — Sales and Inventory System 6.3 Medium 2026-09-04

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