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

Goal: 1000 CNY · Raised: 1336 CNY

100%

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

9906 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-16092 Improved Save Button <= 1.2.1 - Authenticated (Author+) Second-Order SQL Injection via 'meta_key' Parameter — Improved Save Button 6.5 Medium2026-07-30
CVE-2026-48448 Adobe Campaign Classic (ACC) | Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') (CWE-89) — Adobe Campaign Classic 8.6 High2026-07-30
CVE-2026-15929 LG SmartShare<2.3.1712.1202 SQL注入漏洞 — SmartShare 7.1 High2026-07-30
CVE-2026-5490 DriveLock SQL Injection Privilege Escalation Vulnerability — DriveLock--2026-07-29
CVE-2026-8339 SQL Injection in Coverity Connect SOAP API — Coverity Connect 8.7 High2026-07-29
CVE-2026-65890 Joomla Extension - balbooa.com - Unauthenticated SQL injection in Gridbox < 2.20.2 — Gridbox extension for Joomla 9.2 Critical2026-07-29
CVE-2026-33385 Blind SQL Injection in Quick.CMS — Quick.CMS 5.1 Medium2026-07-29
CVE-2026-12895 SQL Injection in Frappe's ERPNext — ERPNext 7.1 High2026-07-29
CVE-2026-11973 WP-Lister Lite for eBay <= 3.8.8 - Authenticated (Administrator+) SQL Injection via 'orderby' Parameter — WP-Lister Lite for eBay 4.9 Medium2026-07-29
CVE-2026-15344 WP Photo Album Plus <= 9.2.04.002 - Authenticated (Administrator+) SQL Injection via 'table' Parameter — WP Photo Album Plus 4.9 Medium2026-07-29
CVE-2026-54658 @hypequery/clickhouse has SQL Injection in parameter escaping that allows arbitrary SQL execution — hypequery 9.8 Critical2026-07-28
CVE-2026-6881 Authenticated SQL Injection Enables Unauthorized Access to Sensitive Information in Ellucian Advance Web and Legacy Advance — Advance Web 9.4 Critical2026-07-28
CVE-2026-11391 Tanium addressed a SQL injection vulnerability in Patch. — Patch 6.3 Medium2026-07-28
CVE-2026-15304 Plugin Organizer <= 10.2.4 - Authenticated (Subscriber+) SQL Injection — Plugin Organizer 6.5 Medium2026-07-28
CVE-2026-7769 SQL injection Security Vulnerability in IBM Sterling B2B Integrator and IBM Sterling File Gateway — Sterling B2B Integrator 8.1 High2026-07-28
CVE-2026-50736 PostgreSQL pglogical提权漏洞 — pglogical 9.0 Critical2026-07-28
CVE-2026-15444 Tutor LMS <= 4.0.1 - Authenticated (Administrator+) SQL Injection via 'coupon_code' Parameter — Tutor LMS – eLearning and online course solution 4.9 Medium2026-07-28
CVE-2026-14785 Web Directory Free <= 1.7.13 - Unauthenticated SQL Injection — Web Directory Free 7.5 High2026-07-28
CVE-2026-10207 PickPlugins Question Answer <= 1.2.73 - Unauthenticated SQL Injection via 'id' Parameter — PickPlugins Question Answer 7.5 High2026-07-28
CVE-2026-16462 SQL injection via unauthenticated GetGridData endpoint — PROCON-WEB SCADA 9.8 Critical2026-07-28
CVE-2026-12800 Premium Packages <= 6.2.0 - Unauthenticated SQL Injection — Premium Packages – Sell Digital Products Securely 7.5 High2026-07-28
CVE-2026-15267 Taskbuilder <= 5.0.9 - Authenticated (Subscriber+) SQL Injection — Taskbuilder – Project Management & Task Management Tool With Kanban Board 6.5 Medium2026-07-28
CVE-2026-13161 TrueBooker <= 1.2.2 - Unauthenticated SQL Injection — TrueBooker – Appointment Booking and Scheduler System 7.5 High2026-07-28
CVE-2026-14516 Online Scheduling and Appointment Booking System <= 27.5 - Unauthenticated SQL Injection — Online Scheduling and Appointment Booking System – Bookly 7.5 High2026-07-28
CVE-2026-12741 WP Fast Total Search <= 1.80.280 - Unauthenticated SQL Injection — WP Fast Total Search – The Power of Indexed Search 7.5 High2026-07-28
CVE-2026-15670 SMS Alert <= 3.9.7 - Authenticated (Administrator+) SQL Injection via 'orderby' Parameter — SMS Alert – SMS & OTP for WooCommerce, Order Notifications & Abandoned Cart Recovery 4.9 Medium2026-07-28
CVE-2026-15673 SMS Alert <= 3.9.7 - Authenticated (Administrator+) SQL Injection via 'checkout_payment_plans' and 'order_status' Settings — SMS Alert – SMS & OTP for WooCommerce, Order Notifications & Abandoned Cart Recovery 4.4 Medium2026-07-28
CVE-2026-15671 SMS Alert <= 3.9.7 - Authenticated (Administrator+) SQL Injection via 'id' Parameter — SMS Alert – SMS & OTP for WooCommerce, Order Notifications & Abandoned Cart Recovery 4.9 Medium2026-07-28
CVE-2026-16811 ShopLentor <= 3.4.5 - Authenticated (Administrator+) SQL Injection via 'orderby' Parameter — ShopLentor – All-in-One WooCommerce Growth & Store Enhancement Plugin 4.9 Medium2026-07-28
CVE-2026-6251 Chaty Pro <= 3.5.5 - Authenticated (Subscriber+) SQL Injection via 'widget_id' Parameter — Chaty Pro 6.5 Medium2026-07-28

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