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

Goal: 1000 CNY · Raised: 1336 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-4761 PHPGurukul Complaint Management System admin-profile.php sql injection — Complaint Management System 7.3 High2025-05-16
CVE-2025-4758 PHPGurukul Beauty Parlour Management System contact.php sql injection — Beauty Parlour Management System 7.3 High2025-05-16
CVE-2025-4757 PHPGurukul Beauty Parlour Management System forgot-password.php sql injection — Beauty Parlour Management System 7.3 High2025-05-16
CVE-2025-4746 Campcodes Sales and Inventory System purchase_delete.php sql injection — Sales and Inventory System 7.3 High2025-05-16
CVE-2025-4743 code-projects Employee Record System getData.php sql injection — Employee Record System 6.3 Medium2025-05-16
CVE-2025-4741 Campcodes Sales and Inventory System purchase_add.php sql injection — Sales and Inventory System 7.3 High2025-05-16
CVE-2025-4739 projectworlds Hospital Database Management System medicines_info.php sql injection — Hospital Database Management System 7.3 High2025-05-16
CVE-2025-4736 PHPGurukul Daily Expense Tracker register.php sql injection — Daily Expense Tracker 7.3 High2025-05-16
CVE-2025-4734 Campcodes Sales and Inventory System ci_update.php sql injection — Sales and Inventory System 7.3 High2025-05-16
CVE-2025-4728 SourceCodester Best Online News Portal search.php sql injection — Best Online News Portal 7.3 High2025-05-15
CVE-2025-4726 itsourcecode Placement Management System view_student.php sql injection — Placement Management System 7.3 High2025-05-15
CVE-2025-4725 itsourcecode Placement Management System view_drive.php sql injection — Placement Management System 7.3 High2025-05-15
CVE-2025-4724 itsourcecode Placement Management System student_profile.php sql injection — Placement Management System 7.3 High2025-05-15
CVE-2025-4723 itsourcecode Placement Management System all_student.php sql injection — Placement Management System 7.3 High2025-05-15
CVE-2025-4722 itsourcecode Placement Management System edit_profile.php sql injection — Placement Management System 7.3 High2025-05-15
CVE-2025-4721 itsourcecode Placement Management System drive.php sql injection — Placement Management System 7.3 High2025-05-15
CVE-2025-4719 Campcodes Sales and Inventory System cash_transaction.php sql injection — Sales and Inventory System 7.3 High2025-05-15
CVE-2025-4718 Campcodes Sales and Inventory System customer_add.php sql injection — Sales and Inventory System 7.3 High2025-05-15
CVE-2025-4717 PHPGurukul Company Visitor Management System visitors-form.php sql injection — Company Visitor Management System 7.3 High2025-05-15
CVE-2025-4716 Campcodes Sales and Inventory System credit_transaction_add.php sql injection — Sales and Inventory System 7.3 High2025-05-15
CVE-2025-4715 Campcodes Sales and Inventory System view_application.php sql injection — Sales and Inventory System 7.3 High2025-05-15
CVE-2025-47785 EMLOG SQL Injection Vulnerability — emlog 8.3 High2025-05-15
CVE-2025-4714 Campcodes Sales and Inventory System reprint.php sql injection — Sales and Inventory System 7.3 High2025-05-15
CVE-2025-4713 Campcodes Sales and Inventory System print.php sql injection — Sales and Inventory System 7.3 High2025-05-15
CVE-2025-4712 Campcodes Sales and Inventory System account_summary.php sql injection — Sales and Inventory System 7.3 High2025-05-15
CVE-2025-4711 Campcodes Sales and Inventory System stockin_add.php sql injection — Sales and Inventory System 7.3 High2025-05-15
CVE-2025-4710 Campcodes Sales and Inventory System transaction.php sql injection — Sales and Inventory System 7.3 High2025-05-15
CVE-2025-4709 Campcodes Sales and Inventory System transaction_del.php sql injection — Sales and Inventory System 7.3 High2025-05-15
CVE-2025-4708 Campcodes Sales and Inventory System sales_add.php sql injection — Sales and Inventory System 7.3 High2025-05-15
CVE-2025-4707 Campcodes Sales and Inventory System transaction_add.php sql injection — Sales and Inventory System 7.3 High2025-05-15

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