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

Goal: 1000 CNY · Raised: 1336 CNY

100%

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

10247 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-10022 code-projects Pharmacy Management System manage_supplier.php sql injection — Pharmacy Management System 6.3 Medium 2024-10-16
CVE-2024-10021 code-projects Pharmacy Management System manage_purchase.php sql injection — Pharmacy Management System 6.3 Medium 2024-10-16
CVE-2021-4450 Post Grid <= 2.1.12 - Contributor+ SQL Injection — Post Grid 8.8 High 2024-10-16
CVE-2016-15040 Kento Post View Counter <= 2.8 - SQL Injection — Kento Post View Counter 9.8 Critical 2024-10-16
CVE-2024-9986 code-projects Blood Bank Management System member_register.php sql injection — Blood Bank Management System 7.3 High 2024-10-15
CVE-2024-9976 code-projects Pharmacy Management System manage_customer.php sql injection — Pharmacy Management System 6.3 Medium 2024-10-15
CVE-2024-9974 SourceCodester Online Eyewear Shop POST Request Master.php sql injection — Online Eyewear Shop 6.3 Medium 2024-10-15
CVE-2024-9973 SourceCodester Online Eyewear Shop Report Viewing Page page sql injection — Online Eyewear Shop 6.3 Medium 2024-10-15
CVE-2024-9925 SQL injection in QPLANT by TAI Smart Factory — QPLANT SF 9.8 Critical 2024-10-15
CVE-2024-9982 ESi Technology AIM LINE Marketing Platform - SQL Injection — AIM LINE Marketing Platform 9.8 Critical 2024-10-15
CVE-2024-9980 FormosaSoft ee-class - SQL Injection — ee-class 8.8 High 2024-10-15
CVE-2024-9972 ChanGate Property Management System - SQL Injection — Property Management System 9.8 Critical 2024-10-15
CVE-2024-9971 NewType FlowMaster BPM Plus - SQL Injection — FlowMaster BPM Plus 8.8 High 2024-10-15
CVE-2024-9968 NewType WebEIP v3.0 - SQL injection — WebEIP 8.8 High 2024-10-15
CVE-2024-9921 TEAMPLUS TECHNOLOGY Team+ - SQL Injection — team+ 9.8 Critical 2024-10-14
CVE-2024-7099 SQL Injection in netease-youdao/qanything — netease-youdao/qanything 9.1 - 2024-10-13
CVE-2024-9918 HuangDou UTCMS sql.php RunSql sql injection — UTCMS 4.7 Medium 2024-10-13
CVE-2024-9905 SourceCodester Online Eyewear Shop sql injection — Online Eyewear Shop 6.3 Medium 2024-10-13
CVE-2024-9894 code-projects Blood Bank System reset.php sql injection — Blood Bank System 6.3 Medium 2024-10-12
CVE-2024-8757 Boost Your Blog's Engagement with WP Post Author <= 3.8.1 - Authenticated (Administrator+) SQL Injection — WP Post Author – Author Box, Multiple Authors, Guest Authors & Custom Avatars 7.2 High 2024-10-12
CVE-2024-48040 WordPress Tainacan plugin <= 0.21.8 - SQL Injection vulnerability — Tainacan 8.5 High 2024-10-11
CVE-2024-47331 WordPress Multi Step for Contact Form plugin <= 2.7.7 - Unauthenticated SQL Injection vulnerability — Multi Step for Contact Form 9.3 Critical 2024-10-11
CVE-2024-48020 WordPress Backup and Staging by WP Time Capsule plugin <= 1.22.21 - SQL Injection vulnerability — Backup and Staging by WP Time Capsule 8.5 High 2024-10-11
CVE-2024-9818 SourceCodester Online Veterinary Appointment System manage_category.php sql injection — Online Veterinary Appointment System 7.3 High 2024-10-10
CVE-2024-9817 code-projects Blood Bank System update.php sql injection — Blood Bank System 6.3 Medium 2024-10-10
CVE-2024-9814 Codezips Pharmacy Management System update.php sql injection — Pharmacy Management System 7.3 High 2024-10-10
CVE-2024-9813 Codezips Pharmacy Management System register.php sql injection — Pharmacy Management System 7.3 High 2024-10-10
CVE-2024-9812 code-projects Crud Operation System delete.php sql injection — Crud Operation System 7.3 High 2024-10-10
CVE-2024-9811 code-projects Restaurant Reservation System filter3.php sql injection — Restaurant Reservation System 7.3 High 2024-10-10
CVE-2024-9809 SourceCodester Online Eyewear Shop Master.php delete_product sql injection — Online Eyewear Shop 6.3 Medium 2024-10-10

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