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

Goal: 1000 CNY · Raised: 1110 CNY

100%

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

9085 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-2025-11613 code-projects Simple Food Ordering System addcategory.php sql injection — Simple Food Ordering System 6.3 Medium2025-10-11
CVE-2025-11612 code-projects Simple Food Ordering System addproduct.php sql injection — Simple Food Ordering System 6.3 Medium2025-10-11
CVE-2025-11611 SourceCodester Simple Inventory System user.php sql injection — Simple Inventory System 6.3 Medium2025-10-11
CVE-2025-11610 SourceCodester Simple Inventory System brand.php sql injection — Simple Inventory System 6.3 Medium2025-10-11
CVE-2025-11608 code-projects E-Banking System POST Parameter register.php sql injection — E-Banking System 7.3 High2025-10-11
CVE-2025-11606 iPynch Social Network Website Search sql injection — Social Network Website 6.3 Medium2025-10-11
CVE-2025-11605 code-projects Client Details System update-profile.php sql injection — Client Details System 6.3 Medium2025-10-11
CVE-2025-11604 projectworlds Online Ordering Food System all-orders.php sql injection — Online Ordering Food System 7.3 High2025-10-11
CVE-2025-11603 code-projects Simple Food Ordering System editproduct.php sql injection — Simple Food Ordering System 6.3 Medium2025-10-11
CVE-2025-11601 SourceCodester Online Student Result System login.php sql injection — Online Student Result System 7.3 High2025-10-11
CVE-2025-11600 code-projects Simple Food Ordering System editcategory.php sql injection — Simple Food Ordering System 6.3 Medium2025-10-11
CVE-2025-11599 Campcodes Online Apartment Visitor Management System forgot-password.php sql injection — Online Apartment Visitor Management System 7.3 High2025-10-11
CVE-2025-11597 code-projects E-Commerce Website product_add_qty.php sql injection — E-Commerce Website 6.3 Medium2025-10-11
CVE-2025-11596 code-projects E-Commerce Website delete_order_details.php sql injection — E-Commerce Website 7.3 High2025-10-11
CVE-2025-11595 Campcodes Online Apartment Visitor Management System admin-profile.php sql injection — Online Apartment Visitor Management System 4.7 Medium2025-10-11
CVE-2025-9947 Custom 404 Pro <= 3.12.0 - Authenticated (Administrator+) SQL Injection via `path` Parameter — Custom 404 Pro 4.9 Medium2025-10-11
CVE-2025-10175 WP Links Page <= 4.9.6 - Authenticated (Subscriber+) SQL Injection — WP Links Page 6.5 Medium2025-10-11
CVE-2025-10185 NEX-Forms – Ultimate Forms Plugin for WordPress <= 9.1.6 - Authenticated (Admin+) SQL Injection — NEX-Forms – Ultimate Forms Plugin for WordPress 4.9 Medium2025-10-11
CVE-2025-10048 My Auctions Allegro Plugin <= 3.6.31 - Authenticated (Admin+) SQL Injection — My auctions allegro 4.9 Medium2025-10-11
CVE-2025-11593 CodeAstro Gym Management System delete-equipment.php sql injection — Gym Management System 6.3 Medium2025-10-11
CVE-2025-11592 CodeAstro Gym Management System edit-equipmentform.php sql injection — Gym Management System 6.3 Medium2025-10-11
CVE-2025-11591 CodeAstro Gym Management System delete-member.php sql injection — Gym Management System 6.3 Medium2025-10-11
CVE-2025-11590 CodeAstro Gym Management System equipment-entry.php sql injection — Gym Management System 6.3 Medium2025-10-11
CVE-2025-11589 CodeAstro Gym Management System user-payment.php sql injection — Gym Management System 6.3 Medium2025-10-10
CVE-2025-11588 CodeAstro Gym Management System index.php sql injection — Gym Management System 6.3 Medium2025-10-10
CVE-2025-11585 code-projects Project Monitoring System useredit.php sql injection — Project Monitoring System 7.3 High2025-10-10
CVE-2025-11584 code-projects Online Job Search Engine searchjob.php sql injection — Online Job Search Engine 7.3 High2025-10-10
CVE-2025-11583 code-projects Online Job Search Engine postjob.php sql injection — Online Job Search Engine 7.3 High2025-10-10
CVE-2025-11582 code-projects Online Job Search Engine registration.php sql injection — Online Job Search Engine 7.3 High2025-10-10
CVE-2025-11558 code-projects E-Commerce Website user_index_search.php sql injection — E-Commerce Website 7.3 High2025-10-09

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