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-33078 Roxy-WI has SQL Injection in haproxy_section_save Endpoint via Unsanitized server_ip Parameter — roxy-wi 9.8AICriticalAI2026-04-24
CVE-2026-31952 Xibo CMS API has SQL Injection via DataSet Filter Parameter — xibo-cms 7.6 High2026-04-24
CVE-2026-41460 SocialEngine <= 7.8.0 SQL Injection via activity/index/get-memberall — SocialEngine 9.8 Critical2026-04-23
CVE-2026-6887 BorG Technology Corporation|Borg SPM 2007 - SQL Injection — Borg SPM 2007 9.8 Critical2026-04-23
CVE-2026-40529 KANATA CMS ALAYA SQL注入漏洞 — CMS ALAYA 6.5AIMediumAI2026-04-23
CVE-2026-41167 Jellystat has SQL Injection that leads to to Remote Code Execution — Jellystat 9.1 Critical2026-04-22
CVE-2026-6833 aEnrich|a+HRD - SQL Injection — a+HRD 6.5 Medium2026-04-22
CVE-2026-41457 OwnTone Server < 29.1 SQL Injection via query and filter Parameters — owntone-server 7.5AIHighAI2026-04-22
CVE-2026-40906 Electric: SQL Injection via ORDER BY Parameter in Shape API — electric 10.0 Critical2026-04-21
CVE-2026-41320 Frappe HR has possibility of SQL Injection due to improper field sanitization — hrms 6.5 Medium2026-04-21
CVE-2026-40887 @vendure/core has a SQL Injection vulnerability — vendure 9.1 Critical2026-04-21
CVE-2025-41029 SQL injection in Zeon Academy Pro by Zeon Global Tech — Zeon Academy Pro 9.8AICriticalAI2026-04-21
CVE-2026-6674 Plugin: CMS für Motorrad Werkstätten <= 1.0.0 - Authenticated (Subscriber+) SQL Injection via 'arttype' Parameter — Plugin: CMS für Motorrad Werkstätten 6.5 Medium2026-04-21
CVE-2026-39946 OpenBao allows SQL Injection in PostgreSQL database secrets engine — openbao 8.8 -2026-04-21
CVE-2026-35588 Glances has CQL Injection in its Cassandra Export Module via Unsanitized Config Values — glances 6.3 Medium2026-04-20
CVE-2025-66335 Apache Doris MCP Server: MCP SQL inject — Apache Doris MCP Server 9.8AICriticalAI2026-04-20
CVE-2026-6629 Metasoft 美特软件 MetaCRM Interface sql.jsp Statement.executeUpdate sql injection — MetaCRM 7.3 High2026-04-20
CVE-2026-6628 phili67 Ecclesia CRM Query Viewer view ValidateInput sql injection — Ecclesia CRM 6.3 Medium2026-04-20
CVE-2026-5964 Digiwin|EasyFlow .NET - SQL Injection — EasyFlow .NET 9.8 Critical2026-04-20
CVE-2026-5963 Digiwin|EasyFlow .NET - SQL Injection — EasyFlow .NET 9.8 Critical2026-04-20
CVE-2026-6595 ProjectsAndPrograms School Management System HTTP GET Parameter buslocation.php sql injection — School Management System 7.3 High2026-04-20
CVE-2026-6562 dameng100 muucmf index.html getListByPage sql injection — muucmf 7.3 High2026-04-19
CVE-2026-40482 ChurchCRM has Authenticated SQL Injection in `/api/families/byCheckNumber/{scanString}` — CRM 8.8AIHighAI2026-04-17
CVE-2026-40285 WeGIA has SQL Injection via Session Variable Override in DespachoControle.php — WeGIA 8.8 High2026-04-17
CVE-2026-6490 QueryMine sms GET Request Parameter deletecourse.php sql injection — sms 7.3 High2026-04-17
CVE-2026-6488 QueryMine sms GET Request Parameter editcourse.php sql injection — sms 6.3 Medium2026-04-17
CVE-2025-15625 Unauthenticated execution of arbitrary SQL queries in Sparx Pro Cloud Server — Sparx Pro Cloud Server 9.8AICriticalAI2026-04-17
CVE-2026-34018 CubeCart 安全漏洞 — CubeCart 9.8AICriticalAI2026-04-17
CVE-2026-6080 Tutor LMS <= 3.9.8 - Authenticated (Admin+) SQL Injection via 'date' Parameter — Tutor LMS – eLearning and online course solution 6.5 Medium2026-04-17
CVE-2026-3330 Form Maker by 10Web <= 1.15.40 - Authenticated (Administrator+) SQL Injection via 'ip_search' Parameter — Form Maker by 10Web – Mobile-Friendly Drag & Drop Contact Form Builder 4.9 Medium2026-04-17

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