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

Goal: 1000 CNY · Raised: 1336 CNY

100%

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

10032 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-10716 Directus <12.1.0 - Authenticated time-based SQL injection in PostgreSQL/PostGIS collection creation — Directus 7.5 High2026-08-05
CVE-2026-71292 Subrion CMS Admin Grid SQL Injection via Unwhitelisted ORDER BY sort Parameter — subrion 7.2 High2026-08-05
CVE-2026-71288 Koha SQL Injection via order_by and {order}_ovalue Parameters in guided_reports.pl — Koha 8.8 High2026-08-05
CVE-2026-71287 Cacti sanitize_sql_column() Regex Allowlist Permits SQL Time-Delay Functions Leading to Blind SQL Injection — cacti 8.8 High2026-08-05
CVE-2026-71282 ChirpStack SQLite Backend SQL Injection via Device Tag Key in ListDevices Filter — chirpstack 6.5 Medium2026-08-05
CVE-2026-71276 Magistrala (formerly Mainflux) IoT Platform SQL Injection via format Query Parameter — magistrala 7.1 High2026-08-05
CVE-2026-71248 Inventory-Management-System-PHP - Unauthenticated SQL Injection in Login and Product Deletion — Inventory-Management-System-PHP 9.8 Critical2026-08-05
CVE-2026-71245 Mautic - SQL Injection via field Parameter in Lead-by-Field-Value AJAX Endpoint — mautic 7.1 High2026-08-05
CVE-2026-71237 Miantang IoT-PHP - Unauthenticated SQL Injection in /userlogin — IoT-PHP 9.8 Critical2026-08-05
CVE-2026-71231 IOTSmartHome - Unauthenticated SQL Injection via lastLogin Cookie — IOTSmartHome 9.8 Critical2026-08-05
CVE-2026-8029 SQL Injection Vulnerability in ZTE SmartLife App — SmartLife 3.9 Low2026-08-05
CVE-2026-11977 WP Post Author <= 3.9.1 - Authenticated (Author+) SQL Injection — WP Post Author – Author Box, Multiple Authors, Guest Authors & Custom Avatars 6.5 Medium2026-08-05
CVE-2026-11920 JoomSport <= 5.7.9 - Authenticated (Administrator+) SQL Injection via 'order' Parameter — JoomSport – for Sports: Team & League, Football, Hockey & more 4.9 Medium2026-08-05
CVE-2026-11969 WP TripAdvisor Review Slider <= 14.3 - Authenticated (Administrator+) SQL Injection — WP TripAdvisor Review Slider 4.9 Medium2026-08-05
CVE-2026-71207 Stock-Inventory-Management-System - Unauthenticated SQL Injection and Hardcoded Credentials in login.php Enable Full Authentication Bypass — Stock-Inventory-Management-System 9.8 Critical2026-08-05
CVE-2026-5651 Askeet <= 3.0 - Authenticated (Administrator+) SQL Injection via 'sql_query' Parameter — Askeet — Talk to Your WooCommerce Data 4.9 Medium2026-08-05
CVE-2026-18881 TableOn <= 1.0.5.1 - Unauthenticated Blind SQL Injection via 'comment_count' Filter Parameter — TableOn – WordPress Posts Table Filterable 7.5 High2026-08-05
CVE-2026-15281 User Access Manager <= 2.3.12 - Authenticated (Subscriber+) SQL Injection — User Access Manager 6.5 Medium2026-08-05
CVE-2026-49004 PostgreSQL Misconfiguration and Command Injection Vulnerability in ZTE NX799J (Red Magic 11 Air) Product — NX799J (Red Magic 11 Air) 6.5 Medium2026-08-05
CVE-2026-5062 PrettyLinks <= 3.6.20 - Authenticated (Administrator+) SQL Injection via 's' Parameter — PrettyLinks – Affiliate Link Management, URL Shortener, Link Cloaking, Tracking & Branded Short Links 4.9 Medium2026-08-05
CVE-2026-15941 Relevanssi <= 4.27.1 and Relevanssi Premium <= 2.30.2 - Authenticated (Contributor+) SQL Injection — Relevanssi Premium – A Better Search 6.5 Medium2026-08-05
CVE-2026-11421 ERP: Complete HR, Accounting & CRM Suite with WooCommerce CRM Support <= 1.17.4 - Authenticated (Custom+) SQL Injection via 'erpadvancefilter' Parameter — ERP: Complete HR, Accounting & CRM Suite Built for WooCommerce 6.5 Medium2026-08-05
CVE-2026-15918 VikAppointments – Services Booking Calendar <= 1.2.19 - Unauthenticated SQL Injection — VikAppointments Services Booking Calendar 7.5 High2026-08-05
CVE-2026-18896 lavkush-maurya Student-Registration-System changepass.php sql injection — Student-Registration-System 6.3 Medium2026-08-05
CVE-2026-18859 ESAFENET CDG usbkey;logindojojs sql injection — CDG 7.3 High2026-08-05
CVE-2026-18854 Shandong Hoteam PDM Product Data Management System DataService GetStoredClassByFilter sql injection — PDM Product Data Management System 7.3 High2026-08-05
CVE-2026-69704 Atals-Livre SQL Injection via Unsanitized GET Parameter in supp() — Atals-Livre 6.5 Medium2026-08-04
CVE-2026-64631 Veeam ONE SQL注入漏洞 — ONE 8.6 High2026-08-04
CVE-2026-18766 chetans9 core-php-admin-panel customers.php sql injection — core-php-admin-panel 6.3 Medium2026-08-04
CVE-2026-70373 Koha - SQL Injection in reports/issues_stats.pl — Koha 8.8 High2026-08-04

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