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

Goal: 1000 CNY · Raised: 1325 CNY

100%

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

9545 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-39479 WordPress Smart Notification Plugin <= 10.3 - SQL Injection vulnerability — Smart Notification 9.3 Critical2025-06-17
CVE-2025-39486 WordPress Rankie plugin < 1.8.2 - SQL Injection vulnerability — Rankie 8.5 High2025-06-17
CVE-2025-47573 WordPress School Management System Plugin <= 92.0.0 - SQL Injection vulnerability — School Management 9.3 Critical2025-06-17
CVE-2025-48118 WordPress Woocommerce Partial Shipment plugin <= 3.2 - SQL Injection Vulnerability — Woocommerce Partial Shipment 8.5 High2025-06-17
CVE-2025-48274 WordPress WP Job Portal plugin <= 2.3.2 - SQL Injection Vulnerability — WP Job Portal 9.3 Critical2025-06-17
CVE-2025-49854 WordPress Slim SEO plugin <= 4.5.4 - SQL Injection Vulnerability — Slim SEO 7.6 High2025-06-17
CVE-2025-6173 Webkul QloApps ajax_products_list.php sql injection — QloApps 4.7 Medium2025-06-17
CVE-2025-6160 SourceCodester Client Database Management System user_customer_create_order.php sql injection — Client Database Management System 7.3 High2025-06-17
CVE-2025-6159 code-projects Hostel Management System allocate_room.php sql injection — Hostel Management System 7.3 High2025-06-17
CVE-2025-6157 PHPGurukul Nipah Virus Testing Management System registered-user-testing.php sql injection — Nipah Virus Testing Management System 7.3 High2025-06-17
CVE-2025-6156 PHPGurukul Nipah Virus Testing Management System bwdates-report-ds.php sql injection — Nipah Virus Testing Management System 6.3 Medium2025-06-17
CVE-2025-6155 PHPGurukul Hostel Management System login-hm.inc.php sql injection — Hostel Management System 7.3 High2025-06-17
CVE-2025-6154 PHPGurukul Hostel Management System login.inc.php sql injection — Hostel Management System 7.3 High2025-06-17
CVE-2025-6153 PHPGurukul Hostel Management System students.php sql injection — Hostel Management System 7.3 High2025-06-17
CVE-2025-5673 Blog2Social <= 8.4.4 - Authenticated (Subscriber+) SQL Injection via `prgSortPostType` Parameter — Blog2Social: Social Media Auto Post & Scheduler 6.5 Medium2025-06-17
CVE-2025-6136 Projectworlds Life Insurance Management System insertPayment.php sql injection — Life Insurance Management System 6.3 Medium2025-06-16
CVE-2025-6135 Projectworlds Life Insurance Management System insertNominee.php sql injection — Life Insurance Management System 6.3 Medium2025-06-16
CVE-2025-6134 Projectworlds Life Insurance Management System insertClient.php sql injection — Life Insurance Management System 6.3 Medium2025-06-16
CVE-2025-6133 Projectworlds Life Insurance Management System insertagent.php sql injection — Life Insurance Management System 6.3 Medium2025-06-16
CVE-2025-6132 Chanjet CRM departmentsetting.php sql injection — CRM 7.3 High2025-06-16
CVE-2025-6124 code-projects Restaurant Order System tablelow.php sql injection — Restaurant Order System 7.3 High2025-06-16
CVE-2025-6123 code-projects Restaurant Order System payment.php sql injection — Restaurant Order System 7.3 High2025-06-16
CVE-2025-6122 code-projects Restaurant Order System table.php sql injection — Restaurant Order System 6.3 Medium2025-06-16
CVE-2025-6118 Das Parking Management System 停车场管理系统 API search sql injection — Parking Management System 停车场管理系统 7.3 High2025-06-16
CVE-2025-6117 Das Parking Management System 停车场管理系统 API Search sql injection — Parking Management System 停车场管理系统 7.3 High2025-06-16
CVE-2025-6116 Das Parking Management System 停车场管理系统 API Search sql injection — Parking Management System 停车场管理系统 7.3 High2025-06-16
CVE-2025-40728 SQL injection vulnerability in Customer Support System — Customer Support System 8.8AIHighAI2025-06-16
CVE-2025-6169 HAMASTAR Technology WIMP website co-construction management platform - SQL Injection — WIMP 9.8 Critical2025-06-16
CVE-2025-6100 realguoshuai open-video-cms list sql injection — open-video-cms 6.3 Medium2025-06-16
CVE-2025-6096 codesiddhant Jasmin Ransomware dashboard.php sql injection — Jasmin Ransomware 6.3 Medium2025-06-15

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