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

Goal: 1000 CNY · Raised: 1359 CNY

100%

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

11015 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-86245 itsourcecode Sales and Inventory System sup_transac.php sql injection — Sales and Inventory System 6.3 Medium 2026-09-07
CVE-2026-86236 itsourcecode Sales and Inventory System pro_transac.php add sql injection — Sales and Inventory System 6.3 Medium 2026-09-07
CVE-2026-86235 itsourcecode Sales and Inventory System pos_transac.php add sql injection — Sales and Inventory System 6.3 Medium 2026-09-06
CVE-2026-86234 itsourcecode Sales and Inventory System cust_transac.php add sql injection — Sales and Inventory System 6.3 Medium 2026-09-06
CVE-2026-86233 itsourcecode Sales and Inventory System us_del.php sql injection — Sales and Inventory System 6.3 Medium 2026-09-06
CVE-2026-86232 itsourcecode Sales and Inventory System sup_del.php sql injection — Sales and Inventory System 6.3 Medium 2026-09-06
CVE-2026-86225 SourceCodester Class and Exam Timetabling System modal_add_room.php mysqli_query sql injection — Class and Exam Timetabling System 7.3 High 2026-09-06
CVE-2026-86224 SourceCodester Class and Exam Timetabling System modal_add_product.php mysqli_query sql injection — Class and Exam Timetabling System 7.3 High 2026-09-06
CVE-2026-86223 SourceCodester Class and Exam Timetabling System modal_add_coursea.php mysqli_query sql injection — Class and Exam Timetabling System 7.3 High 2026-09-06
CVE-2026-86222 SourceCodester Class and Exam Timetabling System modal_add_course2.php mysqli_query sql injection — Class and Exam Timetabling System 7.3 High 2026-09-06
CVE-2026-86221 SourceCodester Class and Exam Timetabling System modal_add_course1.php mysqli_query sql injection — Class and Exam Timetabling System 7.3 High 2026-09-06
CVE-2026-86220 SourceCodester Class and Exam Timetabling System modal_add_course.php mysqli_query sql injection — Class and Exam Timetabling System 7.3 High 2026-09-06
CVE-2026-19634 PostgreSQL Anonymizer: SQL injection in import_database_rules() and import_roles_rules() via crafted object names / JSON — PostgreSQL Anonymizer 6.4 Medium 2026-09-06
CVE-2026-19633 PostgreSQL Anonymizer: unprivileged masked users can execute code via operators, domain casts and view subqueries — PostgreSQL Anonymizer 8.8 High 2026-09-06
CVE-2026-86213 Mstfakts College-Management-System Search university.php mysqli_query sql injection — College-Management-System 7.3 High 2026-09-06
CVE-2026-86211 rabindralamsal inventory-management-system Login index.php sql injection — inventory-management-system 7.3 High 2026-09-06
CVE-2026-86210 SourceCodester Class and Exam Timetabling System delete_user_account.php sql injection — Class and Exam Timetabling System 7.3 High 2026-09-06
CVE-2026-86209 SourceCodester Class and Exam Timetabling System delete_user.php sql injection — Class and Exam Timetabling System 7.3 High 2026-09-06
CVE-2026-86208 SourceCodester Class and Exam Timetabling System delete_teacher.php sql injection — Class and Exam Timetabling System 7.3 High 2026-09-06
CVE-2026-86180 code-projects Task Management System In PHP Login index.php sql injection — Task Management System In PHP 7.3 High 2026-09-06
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

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