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

Goal: 1000 CNY · Raised: 1359 CNY

100%

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

10966 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-103116 OS4ED openSIS-Classic Student List Search Endpoint GetStuListFnc.php DBQuery sql injection — openSIS-Classic 6.3 Medium 2026-09-30
CVE-2026-97293 WordPress Media LIbrary Assistant plugin <= 3.41 - SQL Injection vulnerability — Media LIbrary Assistant 8.5 High 2026-09-30
CVE-2026-97287 WordPress Event Tickets plugin <= 5.29.5 - SQL Injection vulnerability — Event Tickets 8.5 High 2026-09-30
CVE-2026-96828 WordPress Category Discount Woocommerce plugin <= 5.18 - SQL Injection vulnerability — Category Discount Woocommerce 7.6 High 2026-09-30
CVE-2026-96827 WordPress Admin Notices Manager plugin <= 1.6.0 - SQL Injection vulnerability — Admin Notices Manager 7.6 High 2026-09-30
CVE-2026-96822 WordPress Books Gallery plugin <= 4.8.3 - SQL Injection vulnerability — Books Gallery 9.3 Critical 2026-09-30
CVE-2026-96346 WordPress WP ERP plugin <= 1.17.9 - SQL Injection vulnerability — WP ERP 7.6 High 2026-09-30
CVE-2026-96345 WordPress Estatik plugin <= 4.3.5 - SQL Injection vulnerability — Estatik 7.6 High 2026-09-30
CVE-2026-94177 WordPress GamiPress plugin <= 8.0.2 - SQL Injection vulnerability — GamiPress 8.5 High 2026-09-30
CVE-2026-94115 WordPress Easy Pricing Tables plugin <= 4.1.2 - SQL Injection vulnerability — Easy Pricing Tables 8.5 High 2026-09-30
CVE-2026-94082 WordPress Quiz Cat plugin <= 3.1.1 - SQL Injection vulnerability — Quiz Cat 7.6 High 2026-09-30
CVE-2026-93621 WordPress WP Data Access plugin <= 5.5.84 - SQL Injection vulnerability — WP Data Access 8.2 High 2026-09-30
CVE-2026-62085 WordPress WP Activity Log plugin <= 5.6.6 - SQL Injection vulnerability — WP Activity Log 7.6 High 2026-09-30
CVE-2026-103115 OS4ED openSIS-Classic Student Search CustomFieldsFnc.php sql injection — openSIS-Classic 6.3 Medium 2026-09-30
CVE-2026-103114 OS4ED openSIS-Classic Assignment Management Endpoint Assignments.php DBQuery_assignment sql injection — openSIS-Classic 6.3 Medium 2026-09-30
CVE-2026-103113 OS4ED openSIS-Classic General Information Tab Student.php save action sql injection — openSIS-Classic 4.7 Medium 2026-09-30
CVE-2026-102578 Moodle: sql injection in question bank web service 5.5 Medium 2026-09-30
CVE-2026-102456 DigiWin|EasyFlow .NET - SQL Injection — EasyFlow .NET 6.5 Medium 2026-09-30
CVE-2026-16596 WP Directory Kit <= 1.5.4 - Authenticated (Custom+) SQL Injection via 'data_fields_list' Parameter — WP Directory Kit 6.5 Medium 2026-09-30
CVE-2026-6806 Motors <= 1.4.109 - Unauthenticated Blind SQL Injection via 'stm_lat'/'stm_lng' Parameters — Motors – Car Dealership & Classified Listings Plugin 7.5 High 2026-09-30
CVE-2026-102913 SourceCodester Car Driving School Management System Master.php save_enrollment sql injection — Car Driving School Management System 7.3 High 2026-09-30
CVE-2026-102912 SourceCodester Online Leave Management System page reports sql injection — Online Leave Management System 4.7 Medium 2026-09-30
CVE-2026-102910 SourceCodester Online Reviewer Management System exam-delete.php sql injection — Online Reviewer Management System 7.3 High 2026-09-30
CVE-2026-102909 SourceCodester Online Reviewer Management System btn_functions.php sql injection — Online Reviewer Management System 7.3 High 2026-09-30
CVE-2026-102908 SourceCodester Online Reviewer Management System questions-view.php sql injection — Online Reviewer Management System 7.3 High 2026-09-30
CVE-2026-51936 SQLCipher 4.x 之前版本存在 SQL 注入漏洞 — SQLCipher 2.1 Low 2026-09-30
CVE-2026-72507 Toptech TMS7 and TopHAT SQL Injection — TMS7 9.0 Critical 2026-09-29
CVE-2026-68068 Toptech TMS7 and TopHAT SQL Injection — TMS7 9.0 Critical 2026-09-29
CVE-2026-68954 Toptech TMS7 and TopHAT SQL Injection — TMS7 9.0 Critical 2026-09-29
CVE-2026-63713 Toptech TMS7 and TopHAT SQL Injection — TMS7 9.0 Critical 2026-09-29

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