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

Goal: 1000 CNY · Raised: 1000 CNY

100.0%

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

8951 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-44331 ProFTPD 1.3.9a之前存在SQL注入漏洞 — ProFTPD 8.1 High2026-05-05
CVE-2026-33324 SQLBot prompt injection allows arbitrary SQL execution and remote code execution — SQLBot--2026-05-05
CVE-2026-4304 WeePie Cookie Allow <= 3.4.11 - Unauthenticated SQL Injection via 'consent' Parameter — WeePie Cookie Allow 7.5 High2026-05-05
CVE-2026-3359 Form Maker by 10Web – Mobile-Friendly Drag & Drop Contact Form Builder <= 1.15.42 - Unauthenticated SQL Injection via 'inputs' — Form Maker by 10Web – Mobile-Friendly Drag & Drop Contact Form Builder 7.5 High2026-05-05
CVE-2026-40797 WordPress WebinarIgnition plugin <= 4.08.253 - SQL Injection vulnerability — WebinarIgnition 9.3 Critical2026-05-05
CVE-2026-7822 itsourcecode Courier Management System print_pdets.php sql injection — Courier Management System 6.3 Medium2026-05-05
CVE-2026-3456 GeekyBot — Generate AI Content Without Prompt, Chatbot and Lead Generation <= 1.2.0 - Unauthenticated SQL Injection via 'attributekey' — GeekyBot — AI Copilot, Chatbot, WooCommerce Lead Gen & Zero-Prompt Content 7.5 High2026-05-05
CVE-2026-5100 AWP Classifieds <= 4.4.5 - Unauthenticated SQL Injection via 'regions' — AWP Classifieds 7.5 High2026-05-05
CVE-2026-7783 CodeCanyon Perfex CRM Admin Kanban Endpoint AbstractKanban.php applySortQuery sql injection — Perfex CRM 6.3 Medium2026-05-04
CVE-2026-42237 n8n: SQL Injection in Snowflake and MySQL Nodes — n8n 8.8AIHighAI2026-05-04
CVE-2026-42233 n8n: SQL Injection in Oracle Database Node via Limit Field — n8n 8.1AIHighAI2026-05-04
CVE-2026-42229 n8n: SQL Injection in SeaTable Node — n8n 8.1AIHighAI2026-05-04
CVE-2026-42087 OpenC3 COSMOS: SQL Injection in QuestDB Time-Series Data Base — cosmos 9.6 Critical2026-05-04
CVE-2026-7746 SourceCodester Web-based Pharmacy Product Management System edit-admin.php sql injection — Web-based Pharmacy Product Management System 6.3 Medium2026-05-04
CVE-2026-7745 CodeAstro Online Classroom facultydetails sql injection — Online Classroom 6.3 Medium2026-05-04
CVE-2026-7744 CodeAstro Online Classroom addnewstudent sql injection — Online Classroom 6.3 Medium2026-05-04
CVE-2026-7743 CodeAstro Online Classroom studentdetails sql injection — Online Classroom 6.3 Medium2026-05-04
CVE-2026-7742 CodeAstro Online Classroom facultylogin sql injection — Online Classroom 6.3 Medium2026-05-04
CVE-2026-7741 CodeAstro Online Classroom studentlogin sql injection — Online Classroom 6.3 Medium2026-05-04
CVE-2026-7731 code-projects BloodBank Managing System get_state.php sql injection — BloodBank Managing System 6.3 Medium2026-05-04
CVE-2026-7727 Shandong Hoteam Software PDM Product Data Management System DataService GetQueryMachineGridOnePageData sql injection — PDM Product Data Management System 7.3 High2026-05-04
CVE-2026-7716 code-projects Gym Management System In PHP/Windows NT index.php sql injection — Gym Management System In PHP 6.3 Medium2026-05-04
CVE-2026-7699 Dromara MaxKey StrUtils.java StrUtils.checkSqlInjection sql injection — MaxKey 6.3 Medium2026-05-03
CVE-2026-7697 AMTT Hotel Broadband Operation System cardhand_submit.php sql injection — Hotel Broadband Operation System 4.7 Medium2026-05-03
CVE-2026-7695 Acrel Electrical EEMS Enterprise Power Operation and Maintenance Cloud Platform elecMaxMinAvgValue sql injection — EEMS Enterprise Power Operation and Maintenance Cloud Platform 7.3 High2026-05-03
CVE-2026-7694 Acrel Electrical ECEMS Enterprise Microgrid Energy Efficiency Management System elecMaxMinAvgValue sql injection — ECEMS Enterprise Microgrid Energy Efficiency Management System 7.3 High2026-05-03
CVE-2026-7688 Dolibarr ERP CRM Shipments API Endpoint expedition.class.php _checkValForAPI sql injection — ERP CRM 5.0 Medium2026-05-03
CVE-2026-7678 YunaiV yudao-cloud GoViewDataServiceImpl.java getDataBySQL sql injection — yudao-cloud 6.3 Medium2026-05-03
CVE-2026-7672 youlaitech youlai-boot Users Endpoint UserController.java getUserList sql injection — youlai-boot 6.3 Medium2026-05-03
CVE-2026-7670 Jinher OA UserSel.aspx sql injection — OA 7.3 High2026-05-02

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