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

Goal: 1000 CNY · Raised: 1359 CNY

100%

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

10970 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-93980 code-projects Internship Management System Admin Login Form login.php sql injection — Internship Management System 7.3 High 2026-09-20
CVE-2026-93979 code-projects Internship Management System login.php sql injection — Internship Management System 7.3 High 2026-09-20
CVE-2026-93978 code-projects Internship Management System login.php sql injection — Internship Management System 7.3 High 2026-09-20
CVE-2026-93974 SourceCodester Online Reviewer Management System btn_functions.php remove sql injection — Online Reviewer Management System 7.3 High 2026-09-20
CVE-2026-93973 SourceCodester Online Reviewer Management System btn_functions.php remove sql injection — Online Reviewer Management System 7.3 High 2026-09-20
CVE-2026-93972 SourceCodester Online Reviewer Management System btn_functions.php sql injection — Online Reviewer Management System 7.3 High 2026-09-20
CVE-2026-93963 itsourcecode Leave Management System controller.php sql injection — Leave Management System 6.3 Medium 2026-09-20
CVE-2026-93959 SourceCodester Online Reviewer Management System btn_functions.php sql injection — Online Reviewer Management System 7.3 High 2026-09-20
CVE-2026-93983 OpenPanel through 2.3.0 SQL Injection via ClickHouse Property Key Filter — openpanel 5.0 Medium 2026-09-19
CVE-2026-9855 Custom Field Template <= 2.7.8 - Authenticated (Contributor+) SQL Injection via 'post_ID' Parameter — Custom Field Template 6.5 Medium 2026-09-19
CVE-2026-13200 Create <= 2.5.3 - Authenticated (Author+) SQL Injection via 'order' Parameter — Create 6.5 Medium 2026-09-19
CVE-2026-75959 GoPay for WooCommerce <= 1.0.36 - Authenticated (Shop Manager+) SQL Injection via 'log_table_filter' Parameter — GoPay for WooCommerce 4.9 Medium 2026-09-19
CVE-2026-6295 WP Optimizer <= 2.5.0 - Authenticated (Administrator+) SQL Injection via 's' Parameter — WP Optimizer – PageSpeed, Cache, Minify & Core Web Vitals 4.9 Medium 2026-09-19
CVE-2026-13191 Create <= 2.5.3 - Authenticated (Author+) SQL Injection via 'order_by' Parameter — Create 6.5 Medium 2026-09-19
CVE-2026-76899 CordysCRM: Authenticated SQL injection via `sort.name` on `POST /account-pool/page` — CordysCRM 5.7 Medium 2026-09-18
CVE-2026-84239 IBM Guardium Data Protection is affected by multiple vulnerabilities. — Guardium Data Protection 7.6 High 2026-09-18
CVE-2026-84105 IBM Guardium Data Protection is affected by multiple vulnerabilities. — Guardium Data Protection 7.7 High 2026-09-18
CVE-2026-52745 CordysCRM: Customer Public Pool Sorting Field SQL Injection — CordysCRM 5.3 Medium 2026-09-18
CVE-2026-84082 IBM Guardium Data Protection is affected by multiple vulnerabilities. — Guardium Data Protection 9.8 Critical 2026-09-18
CVE-2026-61819 pg_partman privilege escalation via SQL injection in when using pg_jobmon and encountering exception — pg_partman 8.5 High 2026-09-18
CVE-2026-61820 pg_partman privilege escalation via SQL injection when inheriting template properties — pg_partman 8.5 High 2026-09-18
CVE-2026-61817 pg_partman privilege escalation via SQL injection in several functions via time decoder — pg_partman 8.5 High 2026-09-18
CVE-2026-61818 pg_partman SQL injection in undo partition time encoder — pg_partman 8.5 High 2026-09-18
CVE-2026-84073 IBM Guardium Data Protection is affected by multiple vulnerabilities. — Guardium Data Protection 9.1 Critical 2026-09-18
CVE-2026-61781 pg_partman has privilege escalation through SQL injection in create_partition_time() — pg_partman 9.9 Critical 2026-09-18
CVE-2026-84064 IBM Guardium Data Protection is affected by multiple vulnerabilities. — Guardium Data Protection 9.9 Critical 2026-09-18
CVE-2026-81933 IBM Guardium Data Protection is affected by multiple vulnerabilities. — Guardium Data Protection 8.8 High 2026-09-18
CVE-2026-81656 IBM Guardium Data Protection is affected by multiple vulnerabilities. — Guardium Data Protection 8.8 High 2026-09-18
CVE-2026-81626 IBM Guardium Data Protection is affected by multiple vulnerabilities. — Guardium Data Protection 8.6 High 2026-09-18
CVE-2026-80441 IBM Guardium Data Protection is affected by multiple vulnerabilities. — Guardium Data Protection 9.8 Critical 2026-09-18

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