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

Goal: 1000 CNY · Raised: 1325 CNY

100%

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

9424 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-9651 shafhasan chatbox chat.php sql injection — chatbox 6.3 Medium2025-08-29
CVE-2025-9645 itsourcecode Apartment Management System r_all_info.php sql injection — Apartment Management System 7.3 High2025-08-29
CVE-2025-9644 itsourcecode Apartment Management System bill_setup.php sql injection — Apartment Management System 7.3 High2025-08-29
CVE-2025-9643 itsourcecode Apartment Management System utility_bill_setup.php sql injection — Apartment Management System 7.3 High2025-08-29
CVE-2025-9441 iATS Online Forms <= 1.2 - Authenticated (Contributor+) SQL Injection via order Parameter — iATS Online Forms 6.5 Medium2025-08-29
CVE-2025-8858 Changing|Clinic Image System - SQL Injection — Clinic Image System 7.5 High2025-08-29
CVE-2025-9610 code-projects Online Event Judging System create_account.php sql injection — Online Event Judging System 7.3 High2025-08-29
CVE-2025-9608 Portabilis i-Educar Formula de Cálculo de Média view sql injection — i-Educar 6.3 Medium2025-08-29
CVE-2025-9607 Portabilis i-Educar Tabelas de Arredondamento view sql injection — i-Educar 6.3 Medium2025-08-29
CVE-2025-9606 Portabilis i-Educar agenda_preferencias.php sql injection — i-Educar 6.3 Medium2025-08-29
CVE-2025-9601 itsourcecode Apartment Management System employee_salary_setup.php sql injection — Apartment Management System 7.3 High2025-08-29
CVE-2025-9600 itsourcecode Apartment Management System member_type_setup.php sql injection — Apartment Management System 7.3 High2025-08-29
CVE-2025-9599 itsourcecode Apartment Management System month_setup.php sql injection — Apartment Management System 7.3 High2025-08-29
CVE-2025-9598 itsourcecode Apartment Management System year_setup.php sql injection — Apartment Management System 7.3 High2025-08-29
CVE-2025-9597 itsourcecode Apartment Management System rented_all_info.php sql injection — Apartment Management System 7.3 High2025-08-29
CVE-2025-9596 itsourcecode Sports Management System login.php sql injection — Sports Management System 7.3 High2025-08-28
CVE-2025-9594 itsourcecode Apartment Management System complain_info.php sql injection — Apartment Management System 7.3 High2025-08-28
CVE-2025-9593 itsourcecode Apartment Management System unit_status_info.php sql injection — Apartment Management System 7.3 High2025-08-28
CVE-2025-9592 itsourcecode Apartment Management System bill_info.php sql injection — Apartment Management System 7.3 High2025-08-28
CVE-2025-57819 FreePBX Affected by Authentication Bypass Leading to SQL Injection and RCE — endpoint 9.8AICriticalAI2025-08-28
CVE-2025-54720 WordPress Nest Addons Plugin <= 1.6.3 - SQL Injection Vulnerability — Nest Addons 9.3 Critical2025-08-28
CVE-2025-49404 WordPress Listeo-Core Plugin < 2.0.7 - SQL Injection Vulnerability — Listeo Core 8.5 High2025-08-28
CVE-2025-49402 WordPress Exertio Framework Plugin <= 1.3.3 - SQL Injection Vulnerability — Exertio Framework 8.5 High2025-08-28
CVE-2025-39496 WordPress WooBeWoo Product Filter Pro plugin < 2.9.6 - SQL Injection vulnerability — WooBeWoo Product Filter Pro 9.3 Critical2025-08-28
CVE-2025-8977 Simple Download Monitor <= 3.9.33 - Simple Download Monitor <= 3.9.33 – Authenticated (Contributor+) SQL Injection via order parameter in Log Export functionality — Simple Download Monitor 6.5 Medium2025-08-28
CVE-2024-13979 St. Joe ERP System SingleRowQueryConverter SQL Injection — St. Joe ERP System ("圣乔ERP系统") 9.4AICriticalAI2025-08-27
CVE-2025-34162 Bian Que Feijiu Intelligent Emergency and Quality Control System SQL Injection via GetLyfsByParams — Bian Que Feijiu Intelligent Emergency and Quality Control System 9.8AICriticalAI2025-08-27
CVE-2025-9532 Portabilis i-Educar view sql injection — i-Educar 6.3 Medium2025-08-27
CVE-2025-9531 Portabilis i-Educar Agenda agenda.php sql injection — i-Educar 6.3 Medium2025-08-27
CVE-2025-30061 SQL injection in utils/Reporter/OpenReportWindow.pl via the UserID parameter — CGM CLININET 9.8AICriticalAI2025-08-27

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