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

Goal: 1000 CNY · Raised: 1336 CNY

100%

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

10283 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-7515 code-projects Online Appointment Booking System ulocateus.php sql injection — Online Appointment Booking System 7.3 High 2025-07-13
CVE-2025-7514 code-projects Modern Bag contact-list.php sql injection — Modern Bag 7.3 High 2025-07-13
CVE-2025-7513 code-projects Modern Bag slideupdate.php sql injection — Modern Bag 7.3 High 2025-07-13
CVE-2025-7512 code-projects Modern Bag contact-back.php sql injection — Modern Bag 7.3 High 2025-07-13
CVE-2025-7511 code-projects Chat System update_account.php sql injection — Chat System 6.3 Medium 2025-07-13
CVE-2025-7510 code-projects Modern Bag productadd_back.php sql injection — Modern Bag 7.3 High 2025-07-13
CVE-2025-7509 code-projects Modern Bag slide.php sql injection — Modern Bag 7.3 High 2025-07-13
CVE-2025-7508 code-projects Modern Bag product-update.php sql injection — Modern Bag 7.3 High 2025-07-12
CVE-2025-7492 PHPGurukul Vehicle Parking Management System manage-incomingvehicle.php sql injection — Vehicle Parking Management System 6.3 Medium 2025-07-12
CVE-2025-7491 PHPGurukul Vehicle Parking Management System manage-outgoingvehicle.php sql injection — Vehicle Parking Management System 6.3 Medium 2025-07-12
CVE-2025-7490 PHPGurukul Vehicle Parking Management System reg-users.php sql injection — Vehicle Parking Management System 6.3 Medium 2025-07-12
CVE-2025-7489 PHPGurukul Vehicle Parking Management System search-vehicle.php sql injection — Vehicle Parking Management System 6.3 Medium 2025-07-12
CVE-2025-7484 PHPGurukul Vehicle Parking Management System view-outgoingvehicle-detail.php sql injection — Vehicle Parking Management System 6.3 Medium 2025-07-12
CVE-2025-7483 PHPGurukul Vehicle Parking Management System forgot-password.php sql injection — Vehicle Parking Management System 7.3 High 2025-07-12
CVE-2025-7482 PHPGurukul Vehicle Parking Management System print.php sql injection — Vehicle Parking Management System 6.3 Medium 2025-07-12
CVE-2025-7481 PHPGurukul Vehicle Parking Management System profile.php sql injection — Vehicle Parking Management System 6.3 Medium 2025-07-12
CVE-2025-7480 PHPGurukul Vehicle Parking Management System signup.php sql injection — Vehicle Parking Management System 7.3 High 2025-07-12
CVE-2025-7479 PHPGurukul Vehicle Parking Management System view--detail.php sql injection — Vehicle Parking Management System 6.3 Medium 2025-07-12
CVE-2025-7478 code-projects Modern Bag category-list.php sql injection — Modern Bag 7.3 High 2025-07-12
CVE-2025-7476 code-projects Simple Car Rental System approve.php sql injection — Simple Car Rental System 7.3 High 2025-07-12
CVE-2025-7475 code-projects Simple Car Rental System pay.php sql injection — Simple Car Rental System 7.3 High 2025-07-12
CVE-2025-7474 code-projects Job Diary search.php sql injection — Job Diary 7.3 High 2025-07-12
CVE-2025-7471 code-projects Modern Bag login-back.php sql injection — Modern Bag 7.3 High 2025-07-12
CVE-2021-4458 Modern Events Calendar Lite <= 6.3.0 - Unauthenticated SQL Injection — Modern Events Calendar Lite 5.9 Medium 2025-07-12
CVE-2025-7469 Campcodes Sales and Inventory System product_add.php sql injection — Sales and Inventory System 7.3 High 2025-07-12
CVE-2025-7467 code-projects Modern Bag product-detail.php sql injection — Modern Bag 7.3 High 2025-07-12
CVE-2025-7466 1000projects ABC Courier Management add_dealerrequest.php sql injection — ABC Courier Management 7.3 High 2025-07-12
CVE-2025-7461 code-projects Modern Bag action.php sql injection — Modern Bag 7.3 High 2025-07-12
CVE-2025-7459 code-projects Mobile Shop EditMobile.php sql injection — Mobile Shop 7.3 High 2025-07-11
CVE-2025-7457 Campcodes Online Movie Theater Seat Reservation System manage_movie.php sql injection — Online Movie Theater Seat Reservation System 7.3 High 2025-07-11

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