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

Goal: 1000 CNY · Raised: 1336 CNY

100%

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

10013 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-2024-8877 SQL Injection — Netman 204 9.8AICriticalAI2024-09-24
CVE-2024-8436 WP Easy Gallery – WordPress Gallery Plugin <= 4.8.5 - Authenticated (Subscriber+) SQL Injection — WP Easy Gallery – WordPress Gallery Plugin 9.9 Critical2024-09-24
CVE-2024-8624 MDTF – Meta Data and Taxonomies Filter <= 1.3.3.3 - Authenticated (Contributor+) SQL Injection — MDTF – Meta Data and Taxonomies Filter 9.9 Critical2024-09-24
CVE-2024-7735 SQLi in Exnet Informatics Software's Ferry Reservation System — Ferry Reservation System 9.8AICriticalAI2024-09-23
CVE-2024-9094 code-projects Blood Bank System o-.php sql injection — Blood Bank System 6.3 Medium2024-09-23
CVE-2024-9093 SourceCodester Profile Registration without Reload Refresh GET Parameter del.php sql injection — Profile Registration without Reload Refresh 6.3 Medium2024-09-23
CVE-2024-9091 code-projects Student Record System index.php sql injection — Student Record System 7.3 High2024-09-23
CVE-2024-9090 SourceCodester Modern Loan Management System search_member.php sql injection — Modern Loan Management System 6.3 Medium2024-09-22
CVE-2024-9087 code-projects Vehicle Management edit1.php sql injection — Vehicle Management 7.3 High2024-09-22
CVE-2024-9086 code-projects Restaurant Reservation System filter.php sql injection — Restaurant Reservation System 6.3 Medium2024-09-22
CVE-2024-9085 code-projects Restaurant Reservation System index.php sql injection — Restaurant Reservation System 7.3 High2024-09-22
CVE-2024-9081 SourceCodester Online Eyewear Shop view_category.php sql injection — Online Eyewear Shop 6.3 Medium2024-09-22
CVE-2024-9080 code-projects Student Record System pincode-verification.php sql injection — Student Record System 7.3 High2024-09-22
CVE-2024-9079 code-projects Student Record System marks.php sql injection — Student Record System 7.3 High2024-09-22
CVE-2024-9078 code-projects Student Record System course.php sql injection — Student Record System 7.3 High2024-09-22
CVE-2024-47062 Multiple SQL Injections and ORM Leak in navidrome — navidrome 9.1 -2024-09-20
CVE-2024-9041 SourceCodester Best House Rental Management System ajax.php sql injection — Best House Rental Management System 6.3 Medium2024-09-20
CVE-2024-9039 SourceCodester Best House Rental Management System ajax.php sql injection — Best House Rental Management System 7.3 High2024-09-20
CVE-2024-9037 Codezips Internal Marks Calculation index.php sql injection — Internal Marks Calculation 7.3 High2024-09-20
CVE-2024-9035 code-projects Blood Bank Management System Admin Login login.php sql injection — Blood Bank Management System 7.3 High2024-09-20
CVE-2024-9034 code-projects Patient Record Management System login.php sql injection — Patient Record Management System 7.3 High2024-09-20
CVE-2024-9011 code-projects Crud Operation System updata.php sql injection — Crud Operation System 6.3 Medium2024-09-20
CVE-2024-9009 code-projects Online Quiz Site showtest.php sql injection — Online Quiz Site 6.3 Medium2024-09-19
CVE-2024-9008 SourceCodester Best Online News Portal Comment Section news-details.php sql injection — Best Online News Portal 6.3 Medium2024-09-19
CVE-2022-25775 SQL Injection in dynamic Reports — Mautic 6.6 Medium2024-09-18
CVE-2024-5958 SQLi in Eliz Software's Panel — Panel 9.8AICriticalAI2024-09-18
CVE-2024-43969 WordPress Spiffy Calendar plugin <= 4.9.12 - SQL Injection vulnerability — Spiffy Calendar 7.6 High2024-09-17
CVE-2024-43976 WordPress Super Store Finder plugin <= 6.9.7 - SQL Injection vulnerability — Super Store Finder 9.3 Critical2024-09-17
CVE-2024-43978 WordPress Super Store Finder plugin < 6.9.8 - SQL Injection vulnerability — Super Store Finder 9.3 Critical2024-09-17
CVE-2024-44004 WordPress WPCargo Track & Trace plugin <= 8.0.2 - SQL Injection vulnerability — WPCargo Track & Trace 9.3 Critical2024-09-17

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