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

Goal: 1000 CNY · Raised: 1336 CNY

100%

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

9912 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-2025-2831 mingyuefusu 明月复苏 tushuguanlixitong 图书管理系统 bookList getBookList sql injection — tushuguanlixitong 图书管理系统 6.3 Medium2025-03-27
CVE-2025-30217 Frappe has possibility of SQL injection due to improper validations — frappe 7.5AIHighAI2025-03-26
CVE-2025-26941 WordPress Church Admin plugin <= 5.0.18 - SQL Injection vulnerability — Church Admin 9.3 Critical2025-03-26
CVE-2025-28939 WordPress WP Google Calendar Manager plugin <= 2.1 - SQL Injection vulnerability — WP Google Calendar Manager 8.5 High2025-03-26
CVE-2025-28942 WordPress Trust Payments Gateway for WooCommerce plugin <= 1.1.4 - SQL Injection vulnerability — Trust Payments Gateway for WooCommerce 9.3 Critical2025-03-26
CVE-2025-30524 WordPress Product Catalog plugin <= 1.0.4 - SQL Injection vulnerability — Product Catalog 9.3 Critical2025-03-26
CVE-2025-28898 WordPress WP Multistore Locator plugin <= 2.5.2 - SQL Injection vulnerability — WP Multistore Locator 9.3 Critical2025-03-26
CVE-2025-28873 WordPress Shuffle plugin <= 0.5 - SQL Injection vulnerability — Shuffle 8.5 High2025-03-26
CVE-2025-28904 WordPress Web Directory Free plugin <= 1.7.6 - SQL Injection vulnerability — Web Directory Free 9.3 Critical2025-03-25
CVE-2025-30212 Frappe has possibility of SQL injection due to improper validations — frappe 7.5AIHighAI2025-03-25
CVE-2024-53678 Apache VCL: SQL injection vulnerability in New Block Allocation form — Apache VCL 5.3AIMediumAI2025-03-25
CVE-2025-2740 PHPGurukul Old Age Home Management System eligibility.php sql injection — Old Age Home Management System 7.3 High2025-03-25
CVE-2025-2739 PHPGurukul Old Age Home Management System manage-services.php sql injection — Old Age Home Management System 7.3 High2025-03-25
CVE-2025-2738 PHPGurukul Old Age Home Management System manage-scdetails.php sql injection — Old Age Home Management System 7.3 High2025-03-25
CVE-2025-2737 PHPGurukul Old Age Home Management System contactus.php sql injection — Old Age Home Management System 7.3 High2025-03-25
CVE-2025-2736 PHPGurukul Old Age Home Management System bwdates-report-details.php sql injection — Old Age Home Management System 7.3 High2025-03-25
CVE-2025-2735 PHPGurukul Old Age Home Management System add-services.php sql injection — Old Age Home Management System 7.3 High2025-03-25
CVE-2025-2734 PHPGurukul Old Age Home Management System aboutus.php sql injection — Old Age Home Management System 7.3 High2025-03-25
CVE-2024-44903 SirsiDynix Horizon SQL注入漏洞 — IPAC20 7.5 High2025-03-25
CVE-2025-30604 WordPress JiangQie Official Website Mini Program plugin <= 1.8.2 - SQL Injection Vulnerability — JiangQie Official Website Mini Program 7.6 High2025-03-24
CVE-2025-30590 WordPress Flickr set slideshows plugin <= 0.9 - SQL Injection Vulnerability — Flickr set slideshows 8.5 High2025-03-24
CVE-2025-30571 WordPress STEdb Forms plugin <= 1.0.4 - SQL Injection Vulnerability — STEdb Forms 7.6 High2025-03-24
CVE-2025-30570 WordPress دکمه، شبکه اجتماعی خرید plugin <= 2.0.6 - SQL Injection Vulnerability — دکمه، شبکه اجتماعی خرید 7.6 High2025-03-24
CVE-2025-30569 WordPress WP Featured Entries plugin <= - 1.0 SQL Injection Vulnerability — WP Featured Entries 8.5 High2025-03-24
CVE-2025-30525 WordPress WP Profitshare plugin <= 1.4.9 - SQL Injection vulnerability — WP Profitshare 7.6 High2025-03-24
CVE-2025-30523 WordPress Super Simple Subscriptions plugin <= 1.1.0 - SQL Injection vulnerability — Super Simple Subscriptions 7.6 High2025-03-24
CVE-2025-2684 PHPGurukul Bank Locker Management System search-report-details.php sql injection — Bank Locker Management System 7.3 High2025-03-24
CVE-2025-2683 PHPGurukul Bank Locker Management System profile.php sql injection — Bank Locker Management System 7.3 High2025-03-24
CVE-2025-2682 PHPGurukul Bank Locker Management System edit-subadmin.php sql injection — Bank Locker Management System 7.3 High2025-03-24
CVE-2025-2681 PHPGurukul Bank Locker Management System edit-locker.php sql injection — Bank Locker Management System 7.3 High2025-03-24

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