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

Goal: 1000 CNY · Raised: 1336 CNY

100%

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

10269 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-2023-30850 Pimcore SQL Injection Vulnerability in Admin Translations API — pimcore 8.8 High 2023-04-27
CVE-2023-30849 Pimcore vulnerable to SQL Injection in Translation Export API — pimcore 8.8 High 2023-04-27
CVE-2023-30848 Pimcore SQL Injection Vulnerability in Admin Search Find API — pimcore 8.8 High 2023-04-27
CVE-2023-2348 SourceCodester Service Provider Management System manage_user.php sql injection — Service Provider Management System 6.3 Medium 2023-04-27
CVE-2023-2347 SourceCodester Service Provider Management System manage_service.php sql injection — Service Provider Management System 6.3 Medium 2023-04-27
CVE-2023-2346 SourceCodester Service Provider Management System view_inquiry.php sql injection — Service Provider Management System 6.3 Medium 2023-04-27
CVE-2023-2344 SourceCodester Service Provider Management System HTTP POST Request sql injection — Service Provider Management System 6.3 Medium 2023-04-27
CVE-2023-2338 SQL Injection in pimcore/pimcore — pimcore/pimcore 8.8 - 2023-04-27
CVE-2023-30839 PrestaShop vulnerable to SQL filter bypass leading to arbitrary write requests using "SQL Manager" — PrestaShop 10.0 Critical 2023-04-25
CVE-2023-30545 PrestaShop arbitrary file read vulnerability — PrestaShop 7.7 High 2023-04-25
CVE-2023-2244 SourceCodester Online Eyewear Shop GET Parameter update_status.php sql injection — Online Eyewear Shop 6.3 Medium 2023-04-22
CVE-2023-2243 SourceCodester Complaint Management System POST Parameter registration.php sql injection — Complaint Management System 6.3 Medium 2023-04-22
CVE-2023-2242 SourceCodester Online Computer and Laptop Store GET Parameter sql injection — Online Computer and Laptop Store 6.3 Medium 2023-04-22
CVE-2023-2218 SourceCodester Task Reminder System manage_user.php sql injection — Task Reminder System 6.3 Medium 2023-04-21
CVE-2023-2217 SourceCodester Task Reminder System manage_reminder.php sql injection — Task Reminder System 6.3 Medium 2023-04-21
CVE-2023-2215 Campcodes Coffee Shop POS System manage_user.php sql injection — Coffee Shop POS System 6.3 Medium 2023-04-21
CVE-2023-2214 Campcodes Coffee Shop POS System manage_sale.php sql injection — Coffee Shop POS System 6.3 Medium 2023-04-21
CVE-2023-2213 Campcodes Coffee Shop POS System manage_product.php sql injection — Coffee Shop POS System 6.3 Medium 2023-04-21
CVE-2023-2212 Campcodes Coffee Shop POS System view_product.php sql injection — Coffee Shop POS System 6.3 Medium 2023-04-21
CVE-2023-2211 Campcodes Coffee Shop POS System manage_category.php sql injection — Coffee Shop POS System 6.3 Medium 2023-04-21
CVE-2023-2210 Campcodes Coffee Shop POS System view_category.php sql injection — Coffee Shop POS System 6.3 Medium 2023-04-21
CVE-2023-2209 Campcodes Coffee Shop POS System view_details.php sql injection — Coffee Shop POS System 6.3 Medium 2023-04-21
CVE-2023-2208 Campcodes Retro Basketball Shoes Online Store details.php sql injection — Retro Basketball Shoes Online Store 6.3 Medium 2023-04-21
CVE-2023-2207 Campcodes Retro Basketball Shoes Online Store contactus1.php sql injection — Retro Basketball Shoes Online Store 6.3 Medium 2023-04-21
CVE-2023-2206 Campcodes Retro Basketball Shoes Online Store contactus.php sql injection — Retro Basketball Shoes Online Store 6.3 Medium 2023-04-21
CVE-2023-2205 Campcodes Retro Basketball Shoes Online Store login.php sql injection — Retro Basketball Shoes Online Store 6.3 Medium 2023-04-21
CVE-2023-2204 Campcodes Retro Basketball Shoes Online Store faqs.php sql injection — Retro Basketball Shoes Online Store 6.3 Medium 2023-04-21
CVE-2014-125099 I Recommend This Plugin dot-irecommendthis.php sql injection — I Recommend This Plugin 6.3 Medium 2023-04-20
CVE-2023-30605 Multiple SQL injections in sql/instance.py param_edit method in Archery - GHSL-2022-104 — Archery 6.5 Medium 2023-04-18
CVE-2023-30558 Multiple SQL injections in sql/data_dictionary.py table_list method in Archery - GHSL-2022-105 — Archery 6.5 Medium 2023-04-18

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