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

Goal: 1000 CNY · Raised: 1336 CNY

100%

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

10247 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-52887 NocoBase: SQL injection in /api/myInAppChannels:list filter to PG-superuser RCE — nocobase 10.0 Critical 2026-07-15
CVE-2026-45320 DataEase Data Dashboard SqlVariable transFilter Unfiltered SQL Injection — dataease - - 2026-07-15
CVE-2026-45535 DataEase: Stored SQL Injection Vulnerability — dataease - - 2026-07-15
CVE-2026-50030 DataEase: Arbitrary SQL execution in preview path (direct data disclosure) — dataease - - 2026-07-15
CVE-2026-45417 DataEase: SQL injection vulnerability — dataease - - 2026-07-15
CVE-2026-57821 Apache Fineract: Office list: SQL Injection via Subquery in orderBy — Apache Fineract - - 2026-07-15
CVE-2026-35152 Apache Fineract: SQL injection in runreports endpoint — Apache Fineract - - 2026-07-15
CVE-2026-56287 Apache Fineract: Boolean SQL Injection in Client Search API (orderBy parameter) leading to Local File Disclosure — Apache Fineract - - 2026-07-15
CVE-2026-57832 Joomla Extension - joomdonation.com - Unauthenticated blind SQL injection in EDocman < 3.9 — EDocman extension for Joomla 8.7 High 2026-07-15
CVE-2026-57831 Joomla Extension - digital-peak.com - Unauthenticated blind SQL injection in DP Calendar 8.18.0 - 10.11.2 — DP Calendar extension for Joomla 8.7 High 2026-07-15
CVE-2026-15804 MetaGuru|HCM - SQL Injection — HCM 8.8 High 2026-07-15
CVE-2026-11851 ASUS Router SQL注入漏洞 — Router - - 2026-07-15
CVE-2026-48324 ColdFusion | Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') (CWE-89) — ColdFusion 2025 9.1 Critical 2026-07-14
CVE-2026-47992 Adobe Commerce | Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') (CWE-89) — Adobe Commerce 7.2 High 2026-07-14
CVE-2026-45073 Symfony: SQL Injection in PdoAdapter::doClear() via Unsanitized $prefix — symfony - - 2026-07-14
CVE-2026-47295 Microsoft SQL Server Elevation of Privilege Vulnerability — Microsoft SQL Server 2016 Service Pack 3 (GDR) 8.8 High 2026-07-14
CVE-2026-47296 Microsoft SQL Server Elevation of Privilege Vulnerability — Microsoft SQL Server 2016 Service Pack 3 (GDR) 7.5 High 2026-07-14
CVE-2026-15703 SourceCodester Simple and Nice Shopping Cart Script userproductdeletequery.php sql injection — Simple and Nice Shopping Cart Script 7.3 High 2026-07-14
CVE-2026-15736 Multiple SQL/DDL Injection and Arbitrary File Read Vulnerabilities in snowflake-sqlalchemy — Snowflake SQLAlchemy 8.3 High 2026-07-14
CVE-2026-62390 Apache Kylin: SQL Injection Vulnerability in Catalog Cache Refresh API — Apache Kylin - - 2026-07-14
CVE-2026-15183 Input Validation Vulnerabilities in Snowflake Spark Connector — Snowflake Spark Connector - - 2026-07-14
CVE-2026-15676 code-projects Online Job Portal DeleteUser.php sql injection — Online Job Portal 7.3 High 2026-07-14
CVE-2026-15675 code-projects Online Job Portal EditUser.php sql injection — Online Job Portal 7.3 High 2026-07-14
CVE-2026-15672 itsourcecode Electronic Judging System add_judges.php sql injection — Electronic Judging System 6.3 Medium 2026-07-14
CVE-2026-44769 SQL Injection vulnerability in SAP S/4HANA Project Management (PPM-PRO) — SAP S/4HANA Project Management (PPM-PRO) 5.5 Medium 2026-07-14
CVE-2026-15597 SourceCodester Class and Exam Timetabling System edit_exam2.php sql injection — Class and Exam Timetabling System 7.3 High 2026-07-13
CVE-2026-15559 CodeAstro Simple Online Leave Management System POST accept.php sql injection — Simple Online Leave Management System 6.3 Medium 2026-07-13
CVE-2026-15558 CodeAstro Simple Online Leave Management System deletemp.php sql injection — Simple Online Leave Management System 6.3 Medium 2026-07-13
CVE-2026-59515 WordPress AIWU plugin <= 1.5.4 - SQL Injection vulnerability — AIWU 9.3 Critical 2026-07-13
CVE-2026-61955 WordPress گرویتی فرم فارسی plugin <= 3.0.2 - SQL Injection vulnerability — گرویتی فرم فارسی 7.6 High 2026-07-13

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