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

Goal: 1000 CNY · Raised: 1359 CNY

100%

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

11027 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-72853 Budibase before 3.40.0 SQL Injection via Oracle connector — budibase 7.6 High 2026-08-13
CVE-2026-72851 Budibase before 3.40.0 SQL Injection via Unauthenticated Webhook — server 10.0 Critical 2026-08-13
CVE-2026-73663 FreePBX: Unauthenticated SQL injection in FreePBX missedcall via inbound Caller ID name leads to administrator takeover — missedcall 9.3 Critical 2026-08-13
CVE-2026-16961 IBM i is Affected By SQL Injection Vulnerability in Db2 Mirror [] — i 7.6 High 2026-08-13
CVE-2019-25765 ASP-CMS SQL Injection via commentList.asp id Parameter — ASP-CMS 7.5 High 2026-08-13
CVE-2024-58374 Hongjing e-HR Unauthenticated SQL Injection via getSdutyTree — e-HR 7.5 High 2026-08-13
CVE-2026-59109 Zalktis: SQL injection via partner-controlled fields in imported e-invoices — Zalktis 8.8 High 2026-08-13
CVE-2026-73670 CMS Admin SQL Injection via db_data.php table_name Parameter — Saurus CMS Community Edition 7.2 High 2026-08-13
CVE-2026-19710 SourceCodester Simple Student Information System view_department.php sql injection — Simple Student Information System 7.3 High 2026-08-13
CVE-2026-28002 WordPress Booktics plugin 1.0.22 - SQL Injection vulnerability — Booktics 8.5 High 2026-08-13
CVE-2026-73346 WordPress MailChimp For WooCommerce plugin < 6.2 - SQL Injection vulnerability — MailChimp For WooCommerce 7.6 High 2026-08-13
CVE-2026-66658 WordPress Reviewer plugin <= 3.14.2 - SQL Injection vulnerability — Reviewer 8.5 High 2026-08-13
CVE-2026-66478 WordPress Church Admin plugin <= 5.1.1 - SQL Injection vulnerability — Church Admin 9.3 Critical 2026-08-13
CVE-2026-66472 WordPress Everest Backup plugin <= 2.3.12 - SQL Injection vulnerability — Everest Backup 9.3 Critical 2026-08-13
CVE-2026-66458 WordPress RealPress plugin <= 1.1.2 - SQL Injection vulnerability — RealPress 9.3 Critical 2026-08-13
CVE-2026-66446 WordPress If-So Dynamic Content Personalization plugin <= 1.10 - SQL Injection vulnerability — If-So Dynamic Content Personalization 9.3 Critical 2026-08-13
CVE-2026-66436 WordPress Active Products Tables for WooCommerce plugin <= 1.1.1 - SQL Injection vulnerability — Active Products Tables for WooCommerce 9.3 Critical 2026-08-13
CVE-2026-66430 WordPress Visitor Traffic Real Time Statistics Pro plugin <= 11.10 - SQL Injection vulnerability — Visitor Traffic Real Time Statistics Pro 8.5 High 2026-08-13
CVE-2026-61969 WordPress Listdom plugin <= 5.6.0 - SQL Injection vulnerability — Listdom 9.3 Critical 2026-08-13
CVE-2026-61966 WordPress WPJAM Basic plugin <= 7.0.1 - SQL Injection vulnerability — WPJAM Basic 9.3 Critical 2026-08-13
CVE-2026-28168 WordPress CubeWP plugin <= 1.1.30 - SQL Injection vulnerability — CubeWP 8.5 High 2026-08-13
CVE-2026-28156 WordPress Do Lasso plugin <= 358 - SQL Injection vulnerability — Do Lasso 8.5 High 2026-08-13
CVE-2026-28142 WordPress Web Directory Free plugin <= 1.7.13 - SQL Injection vulnerability — Web Directory Free 9.3 Critical 2026-08-13
CVE-2026-28001 WordPress WP Directory Kit plugin <= 1.5.4 - SQL Injection vulnerability — WP Directory Kit 9.3 Critical 2026-08-13
CVE-2026-27538 WordPress WP Directory Kit plugin <= 1.5.4 - SQL Injection vulnerability — WP Directory Kit 7.5 High 2026-08-13
CVE-2026-15741 PostgreSQL expression deparse allows SQL injection via EXTRACT argument — PostgreSQL 8.8 High 2026-08-13
CVE-2026-11840 SQL Injection — ManageEngine Password Manager Pro 8.8 High 2026-08-13
CVE-2026-17111 IBM i is Affected By Multiple Vulnerabilities in SQL — i 7.6 High 2026-08-12
CVE-2026-73332 CamaleonCMS cama_contact_form Plugin Stored XSS via before_html Field — CamaleonCMS 8.7 High 2026-08-12
CVE-2026-72807 SiYuan before v3.7.4 SQL Injection via queryBlocks template — siyuan 8.0 High 2026-08-12

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