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

Goal: 1000 CNY · Raised: 1359 CNY

100%

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

11050 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-5213 projectworlds Responsive E-Learning System delete_file.php sql injection — Responsive E-Learning System 7.3 High 2025-05-26
CVE-2025-5212 PHPGurukul Employee Record Management System editempexp.php sql injection — Employee Record Management System 7.3 High 2025-05-26
CVE-2025-5211 PHPGurukul Employee Record Management System myprofile.php sql injection — Employee Record Management System 7.3 High 2025-05-26
CVE-2025-5210 PHPGurukul Employee Record Management System loginerms.php sql injection — Employee Record Management System 7.3 High 2025-05-26
CVE-2025-5208 SourceCodester Online Hospital Management System check_availability.php sql injection — Online Hospital Management System 7.3 High 2025-05-26
CVE-2025-5207 SourceCodester Client Database Management System superadmin_update_profile.php sql injection — Client Database Management System 4.7 Medium 2025-05-26
CVE-2025-5206 Pixelimity Installation index.php sql injection — Pixelimity 4.7 Medium 2025-05-26
CVE-2025-5205 1000 Projects Daily College Class Work Report Book dcwr_entry.php sql injection — Daily College Class Work Report Book 7.3 High 2025-05-26
CVE-2025-40666 Time-based blind SQL injection vulnerability in TCMAN GIM v11 — GIM 9.8AI Critical AI 2025-05-26
CVE-2025-40665 Time-based blind SQL injection vulnerability in TCMAN GIM v11 — GIM 9.8AI Critical AI 2025-05-26
CVE-2025-5176 Realce Tecnologia Queue Ticket Kiosk Admin Login Page index.php sql injection — Queue Ticket Kiosk 7.3 High 2025-05-26
CVE-2025-5172 Econtrata valida sql injection — Econtrata 7.3 High 2025-05-26
CVE-2025-5170 llisoft MTA Maita Training System AdminShitiController.java AdminShitiListRequestVo sql injection — MTA Maita Training System 6.3 Medium 2025-05-26
CVE-2025-5155 qianfox FoxCMS Article.php batchCope sql injection — FoxCMS 6.3 Medium 2025-05-25
CVE-2025-5152 Chanjet CRM newActivityedit.php sql injection — CRM 6.3 Medium 2025-05-25
CVE-2025-5128 ScriptAndTools Real-Estate-website-in-PHP Admin Login Panel admin sql injection — Real-Estate-website-in-PHP 7.3 High 2025-05-24
CVE-2025-5119 Emlog Pro api_controller.php sql injection — Pro 7.3 High 2025-05-23
CVE-2025-31056 WordPress WhatsCart plugin <= 1.1.0 - SQL Injection vulnerability — WhatsCart - Whatsapp Abandoned Cart Recovery, Order Notifications, Chat Box, OTP for WooCommerce 9.3 Critical 2025-05-23
CVE-2025-31397 WordPress Bus Ticket Booking with Seat Reservation for WooCommerce plugin <= 1.7 - SQL Injection vulnerability — Bus Ticket Booking with Seat Reservation for WooCommerce 9.3 Critical 2025-05-23
CVE-2025-31914 WordPress Pixel Form BuilderPlugin & Autoresponder plugin <= 1.0.2 - SQL Injection Vulnerability — Pixel WordPress Form BuilderPlugin & Autoresponder 9.3 Critical 2025-05-23
CVE-2025-39501 WordPress Goodlayers Hostel plugin <= 3.1.4 - SQL Injection vulnerability — Goodlayers Hostel 9.3 Critical 2025-05-23
CVE-2025-39504 WordPress Goodlayers Hotel plugin <= 3.1.4 - SQL Injection vulnerability — Goodlayers Hotel 9.3 Critical 2025-05-23
CVE-2025-46455 WordPress WP HRM LITE plugin <= 1.1 - SQL Injection Vulnerability — WP HRM LITE 9.3 Critical 2025-05-23
CVE-2025-46463 WordPress Mailing Group Listserv plugin <= 3.0.4 - SQL Injection Vulnerability — Mailing Group Listserv 8.5 High 2025-05-23
CVE-2025-46460 WordPress Easy Guide plugin <= 1.0.0 - SQL Injection Vulnerability — Easy Guide 9.3 Critical 2025-05-23
CVE-2025-46539 WordPress Fable Extra plugin <= 1.0.6 - SQL Injection Vulnerability — Fable Extra 9.3 Critical 2025-05-23
CVE-2025-47478 WordPress ProfileGrid plugin <= 5.9.5.0 - SQL Injection Vulnerability — ProfileGrid 8.5 High 2025-05-23
CVE-2025-47575 WordPress School Management plugin <= 92.0.0 - SQL Injection vulnerability — School Management 8.5 High 2025-05-23
CVE-2025-47599 WordPress Facturante plugin <= 1.11 - SQL Injection Vulnerability — Facturante 9.3 Critical 2025-05-23
CVE-2025-47640 WordPress Printcart Web to Print Product Designer for WooCommerce plugin <= 2.4.0 - SQL Injection Vulnerability — Printcart Web to Print Product Designer for WooCommerce 9.3 Critical 2025-05-23

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