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

Goal: 1000 CNY · Raised: 1000 CNY

100.0%

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

9015 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-13557 Campcodes Online Polling System registeracc.php sql injection — Online Polling System 7.3 High2025-11-23
CVE-2025-13556 Campcodes Online Polling System checklogin.php sql injection — Online Polling System 7.3 High2025-11-23
CVE-2025-13555 Campcodes School File Management System Login index.php sql injection — School File Management System 7.3 High2025-11-23
CVE-2025-13554 Campcodes Supplier Management System Login index.php sql injection — Supplier Management System 7.3 High2025-11-23
CVE-2025-13546 ashraf-kabir travel-agency Search results.php sql injection — travel-agency 6.3 Medium2025-11-23
CVE-2025-13545 ashraf-kabir travel-agency index.php sql injection — travel-agency 4.7 Medium2025-11-23
CVE-2025-66095 WordPress KiviCare plugin <= 3.6.13 - SQL Injection vulnerability — KiviCare 8.5 High2025-11-21
CVE-2025-12750 Groundhogg <= 4.2.6.1 - Authenticated (Admin+) SQL Injection — Groundhogg — CRM, Newsletters, and Marketing Automation 4.9 Medium2025-11-21
CVE-2025-13138 WP Directory Kit <= 1.4.3 - Unauthenticated SQL Injection via select_2_ajax() Function — WP Directory Kit 7.5 High2025-11-21
CVE-2025-13485 itsourcecode Online File Management System ajax.php sql injection — Online File Management System 7.3 High2025-11-21
CVE-2025-13451 SourceCodester Online Shop Project action.php sql injection — Online Shop Project 7.3 High2025-11-20
CVE-2025-13449 code-projects Online Shop Project login.php sql injection — Online Shop Project 7.3 High2025-11-20
CVE-2025-13424 Campcodes Supplier Management System add_product.php sql injection — Supplier Management System 4.7 Medium2025-11-20
CVE-2025-13422 freeprojectscodes Sports Club Management System change_s_pwd.php sql injection — Sports Club Management System 7.3 High2025-11-19
CVE-2025-13421 itsourcecode Human Resource Management System NoticeStore.php sql injection — Human Resource Management System 7.3 High2025-11-19
CVE-2025-13420 itsourcecode Human Resource Management System EventStore.php sql injection — Human Resource Management System 7.3 High2025-11-19
CVE-2025-13410 Campcodes Retro Basketball Shoes Online Store receipt.php sql injection — Retro Basketball Shoes Online Store 7.3 High2025-11-19
CVE-2025-65103 OpenSTAManager has an authenticated SQL Injection vulnerability in API via 'display' parameter — openstamanager 8.8 High2025-11-19
CVE-2025-12743 SQL Injection in Looker Project Generation Endpoint Allows Access to Internal MySQL Database — Looker 6.5AIMediumAI2025-11-19
CVE-2025-65022 i-Educar Authenticated Time-based SQL Injection in `agenda.php` — i-educar 7.2 High2025-11-19
CVE-2025-65023 i-Educar Authenticated Time-based SQL Injection in `funcionario_vinculo_cad.php` — i-educar 7.2 High2025-11-19
CVE-2025-65024 i-Educar Authenticated Time-based SQL Injection in `agenda_admin_cad.php` — i-educar 7.2 High2025-11-19
CVE-2025-13396 code-projects Courier Management System add-office.php sql injection — Courier Management System 6.3 Medium2025-11-19
CVE-2025-10437 SQLi in Exagate's Webpack Management System — Webpack Management System 9.8 Critical2025-11-19
CVE-2025-13395 codehub666 94list function.php login sql injection — 94list 7.3 High2025-11-19
CVE-2025-12646 Community Events <= 1.5.4 - Unauthenticated SQL Injection — Community Events 7.5 High2025-11-19
CVE-2025-65093 LibreNMS is vulnerable to SQL Injection (Boolean-Based Blind) in hostname parameter in ajax_output.php endpoint — librenms 5.5 Medium2025-11-18
CVE-2025-58692 Fortinet FortiVoice SQL注入漏洞 — FortiVoice 7.7 High2025-11-18
CVE-2025-9977 Improper neutralization of input in Times Software E-PAYROLL — E-Payroll 7.5AIHighAI2025-11-18
CVE-2025-13347 SourceCodester Train Station Ticketing System ajax.php sql injection — Train Station Ticketing System 6.3 Medium2025-11-18

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