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

Goal: 1000 CNY · Raised: 1336 CNY

100%

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

9771 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-4164 PHPGurukul Employee Record Management System changepassword.php sql injection — Employee Record Management System 7.3 High2025-05-01
CVE-2025-4163 PHPGurukul Land Record System aboutus.php sql injection — Land Record System 6.3 Medium2025-05-01
CVE-2025-4157 PHPGurukul Boat Booking System booking-details.php sql injection — Boat Booking System 6.3 Medium2025-05-01
CVE-2025-4156 PHPGurukul Boat Booking System change-image.php sql injection — Boat Booking System 6.3 Medium2025-05-01
CVE-2025-4155 PHPGurukul Boat Booking System edit-boat.php sql injection — Boat Booking System 6.3 Medium2025-05-01
CVE-2025-4154 PHPGurukul Pre-School Enrollment System enrollment-details.php sql injection — Pre-School Enrollment System 6.3 Medium2025-05-01
CVE-2025-4153 PHPGurukul Park Ticketing Management System profile.php sql injection — Park Ticketing Management System 7.3 High2025-05-01
CVE-2025-4152 PHPGurukul Online Birth Certificate System bwdates-reports-details.php sql injection — Online Birth Certificate System 7.3 High2025-05-01
CVE-2025-4151 PHPGurukul Curfew e-Pass Management System pass-bwdates-reports-details.php sql injection — Curfew e-Pass Management System 7.3 High2025-05-01
CVE-2025-4113 PHPGurukul Curfew e-Pass Management System edit-pass-detail.php sql injection — Curfew e-Pass Management System 6.3 Medium2025-04-30
CVE-2025-4112 PHPGurukul Student Record System add-course.php sql injection — Student Record System 7.3 High2025-04-30
CVE-2025-4111 PHPGurukul Pre-School Enrollment System visitor-details.php sql injection — Pre-School Enrollment System 6.3 Medium2025-04-30
CVE-2025-4110 PHPGurukul Pre-School Enrollment System edit-teacher.php sql injection — Pre-School Enrollment System 6.3 Medium2025-04-30
CVE-2025-4109 PHPGurukul Pre-School Enrollment System edit-subadmin.php sql injection — Pre-School Enrollment System 6.3 Medium2025-04-30
CVE-2025-4108 PHPGurukul Student Record System add-subject.php sql injection — Student Record System 7.3 High2025-04-30
CVE-2025-2890 tagDiv Opt-In Builder <= 1.7 - Authenticated (Subscriber+) SQL Injection via subscriptionCouponId Parameter — tagDiv Opt-In Builder 6.5 Medium2025-04-30
CVE-2025-4080 PHPGurukul Online Nurse Hiring System view-request.php sql injection — Online Nurse Hiring System 6.3 Medium2025-04-29
CVE-2025-4074 PHPGurukul Curfew e-Pass Management System pass-bwdates-report.php sql injection — Curfew e-Pass Management System 7.3 High2025-04-29
CVE-2025-4073 PHPGurukul Student Record System change-password.php sql injection — Student Record System 7.3 High2025-04-29
CVE-2025-4072 PHPGurukul Online Nurse Hiring System edit-nurse.php sql injection — Online Nurse Hiring System 6.3 Medium2025-04-29
CVE-2025-4071 PHPGurukul COVID19 Testing Management System test-details.php sql injection — COVID19 Testing Management System 7.3 High2025-04-29
CVE-2025-4070 PHPGurukul Rail Pass Management System changeimage.php sql injection — Rail Pass Management System 7.3 High2025-04-29
CVE-2025-40618 SQL injection vulnerability in Bookgy — Bookgy 9.8AICriticalAI2025-04-29
CVE-2025-40617 SQL injection vulnerability in Bookgy — Bookgy 9.8AICriticalAI2025-04-29
CVE-2025-4060 PHPGurukul Notice Board System category.php sql injection — Notice Board System 7.3 High2025-04-29
CVE-2025-4058 Projectworlds Online Examination System Bloodgroop_process.php sql injection — Online Examination System 7.3 High2025-04-29
CVE-2025-4039 PHPGurukul Rail Pass Management System search-pass.php sql injection — Rail Pass Management System 7.3 High2025-04-28
CVE-2025-4034 projectworlds Online Examination System inser_doc_process.php sql injection — Online Examination System 7.3 High2025-04-28
CVE-2025-4033 PHPGurukul Nipah Virus Testing Management System patient-search-report.php sql injection — Nipah Virus Testing Management System 7.3 High2025-04-28
CVE-2025-4031 PHPGurukul Pre-School Enrollment System aboutus.php sql injection — Pre-School Enrollment System 7.3 High2025-04-28

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