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

Goal: 1000 CNY · Raised: 1325 CNY

100%

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

9481 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-7592 PHPGurukul Dairy Farm Shop Management System invoices.php sql injection — Dairy Farm Shop Management System 6.3 Medium2025-07-14
CVE-2025-7591 PHPGurukul Dairy Farm Shop Management System view-invoice.php sql injection — Dairy Farm Shop Management System 6.3 Medium2025-07-14
CVE-2025-7590 PHPGurukul Dairy Farm Shop Management System edit-category.php sql injection — Dairy Farm Shop Management System 6.3 Medium2025-07-14
CVE-2025-7589 PHPGurukul Dairy Farm Shop Management System edit-company.php sql injection — Dairy Farm Shop Management System 6.3 Medium2025-07-14
CVE-2025-7588 PHPGurukul Dairy Farm Shop Management System edit-product.php sql injection — Dairy Farm Shop Management System 6.3 Medium2025-07-14
CVE-2025-7587 code-projects Online Appointment Booking System cover.php sql injection — Online Appointment Booking System 7.3 High2025-07-14
CVE-2025-7585 PHPGurukul Online Fire Reporting System manage-site.php sql injection — Online Fire Reporting System 6.3 Medium2025-07-14
CVE-2025-7584 PHPGurukul Online Fire Reporting System add-team.php sql injection — Online Fire Reporting System 6.3 Medium2025-07-14
CVE-2025-7583 PHPGurukul Online Fire Reporting System all-requests.php sql injection — Online Fire Reporting System 6.3 Medium2025-07-14
CVE-2025-7582 PHPGurukul Online Fire Reporting System assigned-requests.php sql injection — Online Fire Reporting System 6.3 Medium2025-07-14
CVE-2025-7581 code-projects Voting System positions_edit.php sql injection — Voting System 6.3 Medium2025-07-14
CVE-2025-7580 code-projects Voting System positions_row.php sql injection — Voting System 6.3 Medium2025-07-14
CVE-2025-7568 qianfox FoxCMS Video.php batchCope sql injection — FoxCMS 6.3 Medium2025-07-14
CVE-2025-7563 PHPGurukul Online Fire Reporting System completed-requests.php sql injection — Online Fire Reporting System 6.3 Medium2025-07-14
CVE-2025-7562 PHPGurukul Online Fire Reporting System new-requests.php sql injection — Online Fire Reporting System 6.3 Medium2025-07-14
CVE-2025-7561 PHPGurukul Online Fire Reporting System team-ontheway-requests.php sql injection — Online Fire Reporting System 6.3 Medium2025-07-14
CVE-2025-7560 PHPGurukul Online Fire Reporting System workin-progress-requests.php sql injection — Online Fire Reporting System 6.3 Medium2025-07-14
CVE-2025-7559 PHPGurukul Online Fire Reporting System bwdates-report-result.php sql injection — Online Fire Reporting System 6.3 Medium2025-07-14
CVE-2025-7558 code-projects Voting System positions_add.php sql injection — Voting System 6.3 Medium2025-07-14
CVE-2025-7557 code-projects Voting System voters_row.php sql injection — Voting System 6.3 Medium2025-07-14
CVE-2025-7556 code-projects Voting System voters_edit.php sql injection — Voting System 6.3 Medium2025-07-14
CVE-2025-7555 code-projects Voting System voters_add.php sql injection — Voting System 6.3 Medium2025-07-14
CVE-2025-1735 pgsql extension does not check for errors during escaping — PHP 5.9 Medium2025-07-13
CVE-2025-7543 PHPGurukul User Registration & Login and User Management System manage-users.php sql injection — User Registration & Login and User Management System 6.3 Medium2025-07-13
CVE-2025-7542 PHPGurukul User Registration & Login and User Management System user-profile.php sql injection — User Registration & Login and User Management System 7.3 High2025-07-13
CVE-2025-7541 code-projects Online Appointment Booking System get_town.php sql injection — Online Appointment Booking System 7.3 High2025-07-13
CVE-2025-7540 code-projects Online Appointment Booking System getclinic.php sql injection — Online Appointment Booking System 7.3 High2025-07-13
CVE-2025-7539 code-projects Online Appointment Booking System getdoctordaybooking.php sql injection — Online Appointment Booking System 7.3 High2025-07-13
CVE-2025-7537 Campcodes Sales and Inventory System product_update.php sql injection — Sales and Inventory System 7.3 High2025-07-13
CVE-2025-7536 Campcodes Sales and Inventory System receipt_credit.php sql injection — Sales and Inventory System 7.3 High2025-07-13

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