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

Goal: 1000 CNY · Raised: 1325 CNY

100%

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

9402 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-10598 SourceCodester Pet Grooming Management Software search_product.php sql injection — Pet Grooming Management Software 7.3 High2025-09-17
CVE-2025-10597 kidaze CourseSelectionSystem COUNT2.php sql injection — CourseSelectionSystem 7.3 High2025-09-17
CVE-2025-10596 SourceCodester Online Exam Form Submission index.php sql injection — Online Exam Form Submission 7.3 High2025-09-17
CVE-2025-10595 SourceCodester Online Student File Management System delete_user.php sql injection — Online Student File Management System 6.3 Medium2025-09-17
CVE-2025-10594 SourceCodester Online Student File Management System delete_student.php sql injection — Online Student File Management System 6.3 Medium2025-09-17
CVE-2025-10593 SourceCodester Online Student File Management System update_student.php sql injection — Online Student File Management System 6.3 Medium2025-09-17
CVE-2025-10592 itsourcecode Online Public Access Catalog OPAC POST Parameter mysearch.php sql injection — Online Public Access Catalog OPAC 6.3 Medium2025-09-17
CVE-2025-10439 SQLi in Yordam Library Automation System — Yordam Library Automation System 9.8 Critical2025-09-17
CVE-2025-10042 Quiz Maker <= 6.7.0.56 - Unauthenticated SQL Injection — Quiz Maker 5.9 Medium2025-09-17
CVE-2025-10565 Campcodes Grocery Sales and Inventory System ajax.php sql injection — Grocery Sales and Inventory System 7.3 High2025-09-16
CVE-2025-10564 Campcodes Grocery Sales and Inventory System ajax.php sql injection — Grocery Sales and Inventory System 7.3 High2025-09-16
CVE-2025-10563 Campcodes Grocery Sales and Inventory System ajax.php sql injection — Grocery Sales and Inventory System 7.3 High2025-09-16
CVE-2025-10562 Campcodes Grocery Sales and Inventory System ajax.php sql injection — Grocery Sales and Inventory System 7.3 High2025-09-16
CVE-2024-13174 SQLi in E1 Informatics' Web Application — Web Application 8.6 High2025-09-16
CVE-2024-13149 SQLi in Arma Store's Armalife — Armalife 9.8 Critical2025-09-16
CVE-2025-7744 SQLi in Dolusoft's Omaspot — Omaspot 9.8 Critical2025-09-16
CVE-2024-12913 SQLi in Megatek Communication System's Azora Wireless Network Management — Azora Wireless Network Management 8.8 High2025-09-16
CVE-2025-4688 SQLi in BGS Interactive's SINAV.LINK Exam Result Module — SINAV.LINK Exam Result Module 9.8 Critical2025-09-16
CVE-2025-10483 SourceCodester Online Student File Management System save_user.php sql injection — Online Student File Management System 6.3 Medium2025-09-15
CVE-2025-10482 SourceCodester Online Student File Management System index.php sql injection — Online Student File Management System 7.3 High2025-09-15
CVE-2025-10481 SourceCodester Online Student File Management System remove_file.php sql injection — Online Student File Management System 6.3 Medium2025-09-15
CVE-2025-10479 SourceCodester Online Student File Management System index.php sql injection — Online Student File Management System 7.3 High2025-09-15
CVE-2025-10477 kidaze CourseSelectionSystem eligibility.php sql injection — CourseSelectionSystem 6.3 Medium2025-09-15
CVE-2025-10473 yangzongzhuan RuoYi Blacklist SqlUtil.java filterKeyword sql injection — RuoYi 6.3 Medium2025-09-15
CVE-2025-10459 PHPGurukul Beauty Parlour Management System all-appointment.php sql injection — Beauty Parlour Management System 7.3 High2025-09-15
CVE-2025-10448 Campcodes Online Job Finder System index.php sql injection — Online Job Finder System 7.3 High2025-09-15
CVE-2025-10446 Campcodes Computer Sales and Inventory System cust_searchfrm.php sql injection — Computer Sales and Inventory System 7.3 High2025-09-15
CVE-2025-10445 Campcodes Computer Sales and Inventory System us_transac.php sql injection — Computer Sales and Inventory System 7.3 High2025-09-15
CVE-2025-10444 Campcodes Online Job Finder System advancesearch.php sql injection — Online Job Finder System 7.3 High2025-09-15
CVE-2025-10436 Campcodes Computer Sales and Inventory System sup_searchfrm.php sql injection — Computer Sales and Inventory System 7.3 High2025-09-15

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