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

Goal: 1000 CNY · Raised: 1336 CNY

100%

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

10242 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-2024-39887 Apache Superset: Improper SQL authorisation, parse not checking for specific engine functions — Apache Superset 4.3 Medium 2024-07-16
CVE-2023-52290 Apache StreamPark (incubating): Unchecked SQL query fields trigger SQL injection vulnerability — Apache StreamPark (incubating) 6.5AI Medium AI 2024-07-16
CVE-2024-6745 code-projects Simple Ticket Booking Login adminauthenticate.php sql injection — Simple Ticket Booking 7.3 High 2024-07-15
CVE-2024-6743 AguardNet Space Management System - SQL injection — Space Management System 9.8 Critical 2024-07-15
CVE-2024-6736 SourceCodester Employee and Visitor Gate Pass Logging System view_employee.php sql injection — Employee and Visitor Gate Pass Logging System 6.3 Medium 2024-07-15
CVE-2024-6735 itsourcecode Tailoring Management System setgeneral.php sql injection — Tailoring Management System 6.3 Medium 2024-07-15
CVE-2024-6734 itsourcecode Tailoring Management System templateadd.php sql injection — Tailoring Management System 6.3 Medium 2024-07-14
CVE-2024-6733 itsourcecode Tailoring Management System templateedit.php sql injection — Tailoring Management System 6.3 Medium 2024-07-14
CVE-2024-6732 SourceCodester Student Study Center Desk Management System Users.php sql injection — Student Study Center Desk Management System 6.3 Medium 2024-07-14
CVE-2024-6731 SourceCodester Student Study Center Desk Management System Master.php sql injection — Student Study Center Desk Management System 6.3 Medium 2024-07-14
CVE-2024-6729 SourceCodester Kortex Lite Advocate Office Management System add_act.php sql injection — Kortex Lite Advocate Office Management System 6.3 Medium 2024-07-14
CVE-2024-6728 itsourcecode Tailoring Management System typeedit.php sql injection — Tailoring Management System 6.3 Medium 2024-07-14
CVE-2024-39909 SQL Injection in the KubeClarity REST API — kubeclarity 6.5 Medium 2024-07-12
CVE-2024-37564 WordPress PayPlus Payment Gateway plugin <= 7.0.7 - SQL Injection vulnerability — PayPlus Payment Gateway 8.5 High 2024-07-12
CVE-2024-37933 WordPress Woocommerce OpenPos plugin <= 6.4.4 - Unauthenticated SQL Injection vulnerability — Woocommerce OpenPos 9.3 Critical 2024-07-12
CVE-2024-5325 Form Vibes <= 1.4.10 - Authenticated (Subscriber+) SQL Injection via fv_export_data — Form Vibes – Database Manager for Forms 8.8 High 2024-07-12
CVE-2024-6353 Wallet for WooCommerce <= 1.5.4 - Authenticated (Subscriber+) SQL Injection via 'search[value]' — Wallet for WooCommerce 8.8 High 2024-07-12
CVE-2024-6681 witmy my-springsecurity-plus dept sql injection — my-springsecurity-plus 6.3 Medium 2024-07-11
CVE-2024-6680 witmy my-springsecurity-plus build sql injection — my-springsecurity-plus 6.3 Medium 2024-07-11
CVE-2024-6679 witmy my-springsecurity-plus role sql injection — my-springsecurity-plus 6.3 Medium 2024-07-11
CVE-2024-6666 WP ERP <= 1.13.0 - Authenticated (Accounting Manager+) SQL Injection via vendor_id — ERP: Complete HR, Accounting & CRM Suite with WooCommerce CRM Support 8.8 High 2024-07-11
CVE-2024-6676 witmy my-springsecurity-plus user sql injection — my-springsecurity-plus 6.3 Medium 2024-07-11
CVE-2024-6653 code-projects Simple Task List Login loginForm.php sql injection — Simple Task List 7.3 High 2024-07-11
CVE-2024-6652 itsourcecode Gym Management System manage_member.php sql injection — Gym Management System 6.3 Medium 2024-07-10
CVE-2024-37148 GLPI allows account takeover via SQL Injection in AJAX scripts — glpi 8.1 High 2024-07-10
CVE-2024-5792 Houzez CRM <= 1.4.2 - Authenticated (Seller+) SQL Injection — Houzez CRM 8.8 High 2024-07-10
CVE-2024-6527 SQL Injection in MegaBIP — MegaBIP 9.1AI Critical AI 2024-07-09
CVE-2024-37090 SQL Injection vulnerability in multiple StylemixThemes premium themes — Masterstudy Elementor Widgets 8.5 High 2024-07-09
CVE-2024-37112 WordPress WishList Member X plugin < 3.26.7 - Unauthenticated Arbitrary SQL Query Execution vulnerability — WishList Member X 10.0 Critical 2024-07-09
CVE-2024-37225 WordPress Zoho Marketing Automation plugin <= 1.2.7 - SQL Injection vulnerability — Zoho Marketing Automation 8.5 High 2024-07-09

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