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

Goal: 1000 CNY · Raised: 1336 CNY

100%

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

10231 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, Availability Execute 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.
Confidentiality Read Application Data
Since SQL databases generally hold sensitive data, loss of confidentiality is a frequent problem with SQL injection vulnerabilities.
Authentication Gain 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 Control Bypass 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.
Integrity Modify 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 Design Use 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 Design If 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, Operation Run 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 Design For 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.
Implementation While 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 ID Title CVSS Severity Published
CVE-2026-72750 n8n before 1.123.67 SQL Injection via executeQuery Operation — n8n 5.3 Medium 2026-08-11
CVE-2026-72610 Koha Community Koha - Stored SQL Injection via Patron lang Field in Issue Slip Generation — Koha 4.3 Medium 2026-08-11
CVE-2026-72609 Koha Community Koha - SQL Injection via ORDER BY Direction in acqui/parcels.pl — Koha 7.1 High 2026-08-11
CVE-2026-72608 Koha Community Koha - Stored SQL Injection via Patron Card Layout image_name — Koha 6.5 Medium 2026-08-11
CVE-2026-72607 Koha Community Koha - Stored SQL Injection via agefield in Automatic Item Modifications by Age — Koha 7.1 High 2026-08-11
CVE-2026-72599 e107 e107 - SQL Injection — e107 9.8 Critical 2026-08-11
CVE-2026-72562 Pimcore pimcore admin-ui-classic-bundle - SQL Injection — pimcore admin-ui-classic-bundle 8.8 High 2026-08-11
CVE-2026-72558 CiviCRM CiviCRM - SQL Injection — CiviCRM 8.8 High 2026-08-11
CVE-2026-72550 Friendica Friendica - SQL Injection — Friendica 9.8 Critical 2026-08-11
CVE-2026-19425 Win Men Intermational|Travel Agency Management System - SQL Injection — Travel Agency Management System 9.8 Critical 2026-08-11
CVE-2026-66770 SQL Injection vulnerability in SAP Social Intelligence — SAP Social Intelligence 6.3 Medium 2026-08-11
CVE-2026-72908 ERPNext: Possibility of SQL injection due to missing validation — erpnext 6.5 Medium 2026-08-10
CVE-2025-13294 Unauthenticated SQL Injection — TBEA TLogger (TBEA Communication Box 3rd Generation) 9.3 Critical 2026-08-10
CVE-2026-72899 Metabase SQL injection via public card or dashboard — Metabase 10.0 Critical 2026-08-10
CVE-2026-72898 Metabase SQL injection via password reset endpoint — Metabase 10.0 Critical 2026-08-10
CVE-2026-72731 Discourse: Strip SQL comments and use non-recursive parameter interpolation in Data Explorer — discourse 7.1 High 2026-08-10
CVE-2026-63106 ReadyEcommerce < 4.5.2 Unauthenticated SQL Injection via ProductController.php — Ready eCommerce 9.8 Critical 2026-08-10
CVE-2026-72565 Tencent APIJSON - Unauthenticated SQL Injection via @having Operator Map-Form Bypass — APIJSON 9.8 Critical 2026-08-10
CVE-2026-32227 Apache Ranger: SQL Injection vulnerability in lookup functionality — Apache Ranger - - 2026-08-10
CVE-2026-19384 SourceCodester Simple Doctors Appointment System ajax.php set_appointment sql injection — Simple Doctors Appointment System 7.3 High 2026-08-10
CVE-2026-19364 itsourcecode Hospital Management System viewdoctorconsultancycharge.php sql injection — Hospital Management System 6.3 Medium 2026-08-09
CVE-2026-19355 MingSoft MCMS ms-mdiy list.do ModelDataImpl.queryDiyFormData sql injection — MCMS 7.3 High 2026-08-09
CVE-2026-19354 lock-upme OPMS IN Clause message.go sql injection — OPMS 6.3 Medium 2026-08-09
CVE-2026-19351 dresende node-sql-query Request Parameter Select.js SelectQuery.build sql injection — node-sql-query 7.3 High 2026-08-09
CVE-2026-19347 itsourcecode Hospital Management System viewdoctor.php sql injection — Hospital Management System 6.3 Medium 2026-08-09
CVE-2026-19344 code-projects Task Management System comment_count_user.php sql injection — Task Management System 7.3 High 2026-08-09
CVE-2026-19343 code-projects Task Management System AdminLogin.php sql injection — Task Management System 7.3 High 2026-08-09
CVE-2026-19231 SourceCodester Simple Doctors Appointment System ajax.php delete_appointment sql injection — Simple Doctors Appointment System 7.3 High 2026-08-07
CVE-2025-58375 Frappe has potential SQL Injection due to missing validation — frappe 8.1 High 2026-08-07
CVE-2026-19211 SourceCodester Photo Share Website ajax.php signup sql injection — Photo Share Website 7.3 High 2026-08-07

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