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

Goal: 1000 CNY · Raised: 1336 CNY

100%

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

9825 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-3767 PHPGurukul News Portal edit-post.php sql injection — News Portal 6.3 Medium2024-04-15
CVE-2024-3720 Tianwell Fire Intelligent Command Platform API Interface page sql injection — Fire Intelligent Command Platform 6.3 Medium2024-04-13
CVE-2024-3719 Campcodes House Rental Management System ajax.php sql injection — House Rental Management System 6.3 Medium2024-04-13
CVE-2024-3698 Campcodes House Rental Management System manage_payment.php sql injection — House Rental Management System 6.3 Medium2024-04-12
CVE-2024-3697 Campcodes House Rental Management System manage_tenant.php sql injection — House Rental Management System 6.3 Medium2024-04-12
CVE-2024-3696 Campcodes House Rental Management System view_payment.php sql injection — House Rental Management System 6.3 Medium2024-04-12
CVE-2024-3691 PHPGurukul Small CRM Registration Page sql injection — Small CRM 7.3 High2024-04-12
CVE-2024-3690 PHPGurukul Small CRM Change Password sql injection — Small CRM 6.3 Medium2024-04-12
CVE-2024-3688 Xiamen Four-Faith RMP Router Management Platform sql injection — RMP Router Management Platform 6.3 Medium2024-04-12
CVE-2024-3704 SQL Injection vulnerability in OpenGnsys — OpenGnsys 9.8 Critical2024-04-12
CVE-2024-3685 DedeCMS stepselect_main.php sql injection — DedeCMS 6.3 Medium2024-04-12
CVE-2024-3211 Shopping Cart & eCommerce Store <= 5.6.3 - Authenticated (Contributor+) SQL Injection — Shopping Cart & eCommerce Store 8.8 High2024-04-12
CVE-2024-3621 SourceCodester Kortex Lite Advocate Office Management System register_case.php sql injection — Kortex Lite Advocate Office Management System 4.7 Medium2024-04-11
CVE-2024-3620 SourceCodester Kortex Lite Advocate Office Management System adds.php sql injection — Kortex Lite Advocate Office Management System 4.7 Medium2024-04-11
CVE-2024-3619 SourceCodester Kortex Lite Advocate Office Management System addcase_stage.php sql injection — Kortex Lite Advocate Office Management System 4.7 Medium2024-04-11
CVE-2024-3618 SourceCodester Kortex Lite Advocate Office Management System activate_case.php sql injection — Kortex Lite Advocate Office Management System 4.7 Medium2024-04-11
CVE-2024-3617 SourceCodester Kortex Lite Advocate Office Management System deactivate_case.php sql injection — Kortex Lite Advocate Office Management System 4.7 Medium2024-04-11
CVE-2024-31355 WordPress Slideshow Gallery LITE plugin <= 1.7.8 - Auth. SQL Injection vulnerability — Slideshow Gallery 8.5 High2024-04-10
CVE-2024-31356 WordPress User Activity Log plugin <= 1.8 - Auth. SQL Injection vulnerability — User Activity Log 7.6 High2024-04-10
CVE-2024-3540 Campcodes Church Management System add_sundaysch.php sql injection — Church Management System 6.3 Medium2024-04-10
CVE-2024-3539 Campcodes Church Management System addgiving.php sql injection — Church Management System 6.3 Medium2024-04-10
CVE-2024-3538 Campcodes Church Management System addTithes.php sql injection — Church Management System 6.3 Medium2024-04-10
CVE-2024-3537 Campcodes Church Management System admin_user.php sql injection — Church Management System 6.3 Medium2024-04-10
CVE-2024-3536 Campcodes Church Management System delete_log.php sql injection — Church Management System 6.3 Medium2024-04-10
CVE-2024-3535 Campcodes Church Management System index.php sql injection — Church Management System 7.3 High2024-04-10
CVE-2024-3534 Campcodes Church Management System login.php sql injection — Church Management System 7.3 High2024-04-10
CVE-2024-3523 Campcodes Online Event Management System index.php sql injection — Online Event Management System 6.3 Medium2024-04-09
CVE-2024-3522 Campcodes Online Event Management System process.php sql injection — Online Event Management System 6.3 Medium2024-04-09
CVE-2024-0952 WP ERP <= 1.12.9 - Authenticated (Accounting Manager+) SQL Injection via id — ERP: Complete HR, Accounting & CRM Suite with WooCommerce CRM Support 7.2 High2024-04-09
CVE-2024-2341 Appointment Booking Calendar — Simply Schedule Appointments Booking Plugin <= 1.6.7.7 - Authenticated (Subscriber+) SQL Injection — Appointment Booking Calendar — Simply Schedule Appointments Booking Plugin 8.8 High2024-04-09

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