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

Goal: 1000 CNY · Raised: 1000 CNY

100.0%

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

8957 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-2018-25195 Wecodex Hotel CMS 1.0 SQL Injection via Admin Login — Wecodex Hotel CMS 8.2 High2026-03-26
CVE-2018-25183 Shipping System CMS 1.0 SQL Injection via admin login — Shipping System CMS 8.2 High2026-03-26
CVE-2018-25185 Wecodex Restaurant CMS 1.0 SQL Injection via Login — Wecodex Restaurant CMS 8.2 High2026-03-26
CVE-2026-4850 code-projects Simple Laundry System Parameter checkregisitem.php sql injection — Simple Laundry System 7.3 High2026-03-26
CVE-2026-4844 code-projects Online Food Ordering System Admin Login admin.php sql injection — Online Food Ordering System 7.3 High2026-03-26
CVE-2026-4842 itsourcecode Online Enrollment System Parameter index.php sql injection — Online Enrollment System 7.3 High2026-03-26
CVE-2026-4841 code-projects Online Food Ordering System Shopping Cart cart.php sql injection — Online Food Ordering System 7.3 High2026-03-26
CVE-2026-4839 SourceCodester Food Ordering System Parameter purchase.php sql injection — Food Ordering System 7.3 High2026-03-26
CVE-2026-4838 SourceCodester Malawi Online Market display.php sql injection — Malawi Online Market 7.3 High2026-03-26
CVE-2026-4836 code-projects Accounting System delete.php sql injection — Accounting System 6.3 Medium2026-03-26
CVE-2026-4826 SourceCodester Sales and Inventory System HTTP GET Parameter update_stock.php sql injection — Sales and Inventory System 6.3 Medium2026-03-25
CVE-2026-33917 OpenEMR has SQL Injection in CAMOS Form — openemr 8.8 High2026-03-25
CVE-2026-33914 OpenEMR has SQL Injection in PostCalendar Category Delete — openemr 7.2 High2026-03-25
CVE-2026-33910 OpenEMR has a SQL Injection Vulnerability in patient selection — openemr 7.2 High2026-03-25
CVE-2026-33909 OpenEMR Vulnerable to SQL Injection via Unsanitized Variables in MedEx Recall/Reminder Processing — openemr 5.9 Medium2026-03-25
CVE-2026-4825 SourceCodester Sales and Inventory System HTTP GET Parameter update_sales.php sql injection — Sales and Inventory System 6.3 Medium2026-03-25
CVE-2026-29187 OpenEMR Vulnerable to Authenticated Blind Boolean-Based SQL Injection in new_search_popup.php — openemr 8.1 High2026-03-25
CVE-2026-33713 n8n Vulnerable to SQL Injection in Data Table Node via orderByColumn Expression — n8n 8.8 -2026-03-25
CVE-2026-32539 WordPress PublishPress Revisions plugin <= 3.7.23 - SQL Injection vulnerability — PublishPress Revisions 9.3 Critical2026-03-25
CVE-2026-32534 WordPress JS Help Desk plugin <= 3.0.3 - SQL Injection vulnerability — JS Help Desk 8.5 High2026-03-25
CVE-2026-32516 WordPress Miraculous Core Plugin plugin < 2.1.2 - SQL Injection vulnerability — Miraculous Core Plugin 8.5 High2026-03-25
CVE-2026-32499 WordPress ChatBot plugin <= 7.7.9 - SQL Injection vulnerability — ChatBot 9.3 Critical2026-03-25
CVE-2026-31920 WordPress Product Rearrange for WooCommerce plugin <= 1.2.2 - SQL Injection vulnerability — Product Rearrange for WooCommerce 9.3 Critical2026-03-25
CVE-2026-27039 WordPress WZone plugin <= 14.0.31 - SQL Injection vulnerability — WZone 8.5 High2026-03-25
CVE-2026-25377 WordPress Addon Jobsearch Chat plugin <= 3.0 - SQL Injection vulnerability — Addon Jobsearch Chat 9.3 Critical2026-03-25
CVE-2026-25371 WordPress Lumise Product Designer plugin < 2.0.9 - SQL Injection vulnerability — Lumise Product Designer 9.3 Critical2026-03-25
CVE-2026-25340 WordPress Jobmonster theme < 4.8.4 - SQL Injection vulnerability — Jobmonster 9.3 Critical2026-03-25
CVE-2026-25007 WordPress ElementInvader Addons for Elementor plugin <= 1.4.2 - SQL Injection vulnerability — ElementInvader Addons for Elementor 8.5 High2026-03-25
CVE-2026-24993 WordPress Advanced WooCommerce Product Sales Reporting plugin <= 4.1.3 - SQL Injection vulnerability — Advanced WooCommerce Product Sales Reporting 9.3 Critical2026-03-25
CVE-2026-24977 WordPress Organici Library plugin <= 2.1.2 - SQL Injection vulnerability — Organici Library 8.5 High2026-03-25

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