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-6891 code-projects Inventory Management System createUser.php sql injection — Inventory Management System 7.3 High 2025-06-30
CVE-2025-6890 code-projects Movie Ticketing System ticketConfirmation.php sql injection — Movie Ticketing System 6.3 Medium 2025-06-30
CVE-2025-6889 code-projects Movie Ticketing System logIn.php sql injection — Movie Ticketing System 7.3 High 2025-06-30
CVE-2025-6888 PHPGurukul Teachers Record Management System changeimage.php sql injection — Teachers Record Management System 7.3 High 2025-06-30
CVE-2025-6885 PHPGurukul Teachers Record Management System edit-teacher-detail.php sql injection — Teachers Record Management System 7.3 High 2025-06-30
CVE-2025-6884 code-projects Staff Audit System search_index.php sql injection — Staff Audit System 6.3 Medium 2025-06-30
CVE-2025-6883 code-projects Staff Audit System update_index.php sql injection — Staff Audit System 6.3 Medium 2025-06-30
CVE-2025-6880 SourceCodester Best Salon Management System edit-tax.php sql injection — Best Salon Management System 6.3 Medium 2025-06-30
CVE-2025-6879 SourceCodester Best Salon Management System add-tax.php sql injection — Best Salon Management System 6.3 Medium 2025-06-30
CVE-2025-6878 SourceCodester Best Salon Management System search-appointment.php sql injection — Best Salon Management System 6.3 Medium 2025-06-30
CVE-2025-6877 SourceCodester Best Salon Management System edit-category.php sql injection — Best Salon Management System 6.3 Medium 2025-06-29
CVE-2025-6876 SourceCodester Best Salon Management System add-category.php sql injection — Best Salon Management System 6.3 Medium 2025-06-29
CVE-2025-6875 SourceCodester Best Salon Management System edit-subscription.php sql injection — Best Salon Management System 6.3 Medium 2025-06-29
CVE-2025-6874 SourceCodester Best Salon Management System add_subscribe.php sql injection — Best Salon Management System 6.3 Medium 2025-06-29
CVE-2025-6871 SourceCodester Simple Company Website Login.php sql injection — Simple Company Website 7.3 High 2025-06-29
CVE-2025-6869 SourceCodester Simple Company Website manage.php sql injection — Simple Company Website 4.7 Medium 2025-06-29
CVE-2025-6868 SourceCodester Simple Company Website manage.php sql injection — Simple Company Website 4.7 Medium 2025-06-29
CVE-2025-6867 SourceCodester Simple Company Website manage.php sql injection — Simple Company Website 4.7 Medium 2025-06-29
CVE-2025-6863 PHPGurukul Local Services Search Engine Management System edit-category-detail.php sql injection — Local Services Search Engine Management System 7.3 High 2025-06-29
CVE-2025-6862 SourceCodester Best Salon Management System edit_plan.php sql injection — Best Salon Management System 6.3 Medium 2025-06-29
CVE-2025-6861 SourceCodester Best Salon Management System add_plan.php sql injection — Best Salon Management System 6.3 Medium 2025-06-29
CVE-2025-6860 SourceCodester Best Salon Management System staff_commision.php sql injection — Best Salon Management System 6.3 Medium 2025-06-29
CVE-2025-6859 SourceCodester Best Salon Management System pro_sale.php sql injection — Best Salon Management System 6.3 Medium 2025-06-29
CVE-2025-6850 code-projects Simple Forum forum1.php sql injection — Simple Forum 6.3 Medium 2025-06-29
CVE-2025-6847 code-projects Simple Forum forum_edit.php sql injection — Simple Forum 6.3 Medium 2025-06-29
CVE-2025-6846 code-projects Simple Forum forum_viewfile.php sql injection — Simple Forum 7.3 High 2025-06-29
CVE-2025-6845 code-projects Simple Forum register1.php sql injection — Simple Forum 7.3 High 2025-06-29
CVE-2025-6844 code-projects Simple Forum signin.php sql injection — Simple Forum 7.3 High 2025-06-29
CVE-2025-6842 code-projects Product Inventory System edit_user.php sql injection — Product Inventory System 4.7 Medium 2025-06-29
CVE-2025-6841 code-projects Product Inventory System edit_product.php sql injection — Product Inventory System 4.7 Medium 2025-06-29

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