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

Goal: 1000 CNY · Raised: 1359 CNY

100%

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

11075 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-2025-11313 Tipray 厦门天锐科技股份有限公司 Data Leakage Prevention System 天锐数据泄露防护系统 findRolePage.do findRolePage sql injection — Data Leakage Prevention System 天锐数据泄露防护系统 7.3 High 2025-10-06
CVE-2025-11312 Tipray 厦门天锐科技股份有限公司 Data Leakage Prevention System 天锐数据泄露防护系统 findModulePage.do findModulePage sql injection — Data Leakage Prevention System 天锐数据泄露防护系统 7.3 High 2025-10-06
CVE-2025-11311 Tipray 厦门天锐科技股份有限公司 Data Leakage Prevention System 天锐数据泄露防护系统 findTenantPage.do findTenantPage sql injection — Data Leakage Prevention System 天锐数据泄露防护系统 7.3 High 2025-10-06
CVE-2025-11310 Tipray 厦门天锐科技股份有限公司 Data Leakage Prevention System 天锐数据泄露防护系统 findFileServerPage.do findFileServerPage sql injection — Data Leakage Prevention System 天锐数据泄露防护系统 7.3 High 2025-10-05
CVE-2025-11309 Tipray 厦门天锐科技股份有限公司 Data Leakage Prevention System 天锐数据泄露防护系统 findDeptPage.do doFilter sql injection — Data Leakage Prevention System 天锐数据泄露防护系统 7.3 High 2025-10-05
CVE-2025-11288 CRMEB GET Parameter product sql injection — CRMEB 6.3 Medium 2025-10-05
CVE-2025-10692 OpenSupports 4.11.0 — SQL Injection — OpenSupports 7.1AI High AI 2025-10-03
CVE-2025-54153 Qsync Central — Qsync Central 9.8 - 2025-10-03
CVE-2025-53595 Qsync Central — Qsync Central 9.8 - 2025-10-03
CVE-2024-56804 Video Station — Video Station 9.8 - 2025-10-03
CVE-2025-40636 SQL injection in the mod_vvisit_counter module — mod_vvisit_counter 7.5AI High AI 2025-10-03
CVE-2025-10582 WP Dispatcher <= 1.2.0 - Authenticated (Contributor+) SQL Injection — WP Dispatcher 8.8 High 2025-10-03
CVE-2025-9200 Blappsta Mobile App Plugin – Your native, mobile iPhone App and Android App <= 0.8.8.8 - Unauthenticated SQL Injection — Blappsta Mobile App Plugin – Your native, mobile iPhone App and Android App 7.5 High 2025-10-03
CVE-2025-9199 Woo superb slideshow transition gallery with random effect <= 9.1 - Authenticated (Contributor+) SQL Injection — Woo superb slideshow transition gallery with random effect 6.5 Medium 2025-10-03
CVE-2025-9198 Wp cycle text announcement <= 8.1 - Authenticated (Contributor+) SQL Injection — Wp cycle text announcement 6.5 Medium 2025-10-03
CVE-2025-10726 WPRecovery <= 2.0 - Unauthenticated SQL Injection to Arbitrary File Deletion — WPRecovery 9.1 Critical 2025-10-03
CVE-2025-0616 SQLi in Teknolojik Center Telecommunication's B2B - Netsis Panel — B2B - Netsis Panel 8.2 High 2025-10-03
CVE-2025-61605 WeGIA: SQL Injection (Blind Time-Based) Vulnerability in /pet/profile_pet.php Endpoint — WeGIA 9.8 - 2025-10-02
CVE-2025-61603 WeGIA: SQL Injection (Blind Time-Based) Vulnerability in API `descricao` Parameter — WeGIA 9.8 - 2025-10-02
CVE-2025-59743 Multiple vulnerabilities in AndSoft's e-TMS — e-TMS 9.8 - 2025-10-02
CVE-2025-59742 Multiple vulnerabilities in AndSoft's e-TMS — e-TMS 9.8 - 2025-10-02
CVE-2025-11020 Remote Code Execution in MarkAny SafePC Enterprise — SafePC Enterprise 8.8 High 2025-10-02
CVE-2025-59681 Django SQL注入漏洞 — Django 7.1 High 2025-10-01
CVE-2025-8122 Blind SQL Injection in PAD CMS — PAD CMS 8.8AI High AI 2025-09-30
CVE-2025-8121 Blind SQL Injection in PAD CMS — PAD CMS 8.8AI High AI 2025-09-30
CVE-2025-8877 AffiliateWP <= 2.28.2 - Unauthenticated SQL Injection — AffiliateWP 7.5 High 2025-09-30
CVE-2024-13150 SQLi in Fayton Software's fayton.pro ERP — fayton.pro ERP 9.8 Critical 2025-09-29
CVE-2025-6724 Chef Automate SQL Injection Vulnerability — Chef Automate 8.8 High 2025-09-29
CVE-2025-11118 CodeAstro Student Grading System adminLogin.php sql injection — Student Grading System 7.3 High 2025-09-28
CVE-2025-11116 code-projects Simple Scheduling System add.home.php sql injection — Simple Scheduling System 7.3 High 2025-09-28

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