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

Goal: 1000 CNY · Raised: 1000 CNY

100.0%

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

8957 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-2026-1179 Yonyou KSOA HTTP GET Parameter user_popedom.jsp sql injection — KSOA 7.3 High2026-01-19
CVE-2026-1178 Yonyou KSOA HTTP GET Parameter select.jsp sql injection — KSOA 7.3 High2026-01-19
CVE-2026-1177 Yonyou KSOA HTTP GET Parameter save_folder.jsp sql injection — KSOA 7.3 High2026-01-19
CVE-2026-1176 itsourcecode School Management System index.php sql injection — School Management System 7.3 High2026-01-19
CVE-2026-22850 Koko Analytics vulnerable to arbitrary SQL execution through unescaped analytics export/import and permissive admin SQL import — koko-analytics 8.4 High2026-01-19
CVE-2026-1160 PHPGurukul Directory Management System Search index.php sql injection — Directory Management System 7.3 High2026-01-19
CVE-2026-1159 itsourcecode Online Frozen Foods Ordering System order_online.php sql injection — Online Frozen Foods Ordering System 7.3 High2026-01-19
CVE-2026-0610 Devolutions Server 安全漏洞 — Server 8.8AIHighAI2026-01-19
CVE-2026-1133 Yonyou KSOA HTTP GET Parameter folder.jsp sql injection — KSOA 7.3 High2026-01-19
CVE-2026-1132 Yonyou KSOA HTTP GET Parameter edit_folder.jsp sql injection — KSOA 7.3 High2026-01-19
CVE-2026-1131 Yonyou KSOA HTTP GET Parameter save_catalog.jsp sql injection — KSOA 7.3 High2026-01-19
CVE-2026-1130 Yonyou KSOA HTTP GET Parameter worksadd_plan.jsp sql injection — KSOA 7.3 High2026-01-19
CVE-2026-1129 Yonyou KSOA HTTP GET Parameter worksadd.jsp sql injection — KSOA 7.3 High2026-01-19
CVE-2026-1124 Yonyou KSOA HTTP GET Parameter work_report.jsp sql injection — KSOA 7.3 High2026-01-18
CVE-2026-1123 Yonyou KSOA HTTP GET Parameter work_mod.jsp sql injection — KSOA 7.3 High2026-01-18
CVE-2026-1122 Yonyou KSOA HTTP GET Parameter work_info.jsp sql injection — KSOA 7.3 High2026-01-18
CVE-2026-1121 Yonyou KSOA HTTP GET Parameter del_workplan.jsp sql injection — KSOA 7.3 High2026-01-18
CVE-2026-1120 Yonyou KSOA HTTP GET Parameter del_work.jsp sql injection — KSOA 7.3 High2026-01-18
CVE-2026-1119 itsourcecode Society Management System delete_activity.php sql injection — Society Management System 7.3 High2026-01-18
CVE-2026-1118 itsourcecode Society Management System add_activity.php sql injection — Society Management System 6.3 Medium2026-01-18
CVE-2026-1105 EasyCMS UserAction.class.php sql injection — EasyCMS 7.3 High2026-01-17
CVE-2026-1059 FeMiner wms chkuser.php sql injection — wms 7.3 High2026-01-17
CVE-2026-1050 risesoft-y9 Digital-Infrastructure REST Authenticate Endpoint Y9PlatformUtil.java sql injection — Digital-Infrastructure 7.3 High2026-01-17
CVE-2025-12984 Advanced Ads – Ad Manager & AdSense <= 2.0.15 - Authenticated (Admin+) SQL Injection — Advanced Ads – Ad Manager & AdSense 4.9 Medium2026-01-17
CVE-2026-23723 WeGIA has a Critical SQL Injection in Atendido_ocorrenciaControle via id_memorando parameter — WeGIA 7.2 High2026-01-16
CVE-2025-61943 AVEVA Process Optimization SQL Injection — Process Optimization 8.4 High2026-01-16
CVE-2021-47811 Grocery crud 1.6.4 - 'order_by' SQL Injection — Grocery crud 9.1 Critical2026-01-15
CVE-2021-47801 Vianeos OctoPUS 5 - 'login_user' SQLi — Vianeos OctoPUS 8.2 High2026-01-15
CVE-2021-47782 Odine Solutions GateKeeper 1.0 - 'trafficCycle' SQL Injection — Odine Solutions GateKeeper 8.2 High2026-01-15
CVE-2025-66417 GLPI has an unauthenticated SQL injection through the inventory endpoint — glpi 7.5 High2026-01-15

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