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

Goal: 1000 CNY · Raised: 1336 CNY

100%

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

10255 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-0360 PHPGurukul Hospital Management System edit-doctor-specialization.php sql injection — Hospital Management System 5.5 Medium 2024-01-10
CVE-2024-0359 code-projects Simple Online Hotel Reservation System login.php sql injection — Simple Online Hotel Reservation System 7.3 High 2024-01-10
CVE-2024-0357 coderd-repos Eva HTTP POST Request page sql injection — Eva 5.5 Medium 2024-01-10
CVE-2024-0355 PHPGurukul Dairy Farm Shop Management System add-category.php sql injection — Dairy Farm Shop Management System 5.5 Medium 2024-01-09
CVE-2024-0344 soxft TimeMail check.php sql injection — TimeMail 5.5 Medium 2024-01-09
CVE-2024-0342 Inis Sqlite.php sql injection — Inis 6.3 Medium 2024-01-09
CVE-2023-52142 WordPress Events Shortcodes & Templates For The Events Calendar Plugin <= 2.3.1 is vulnerable to SQL Injection — Events Shortcodes For The Events Calendar 7.6 High 2024-01-08
CVE-2023-52201 WordPress pTypeConverter Plugin <= 0.2.8.1 is vulnerable to SQL Injection — pTypeConverter 7.6 High 2024-01-08
CVE-2023-52204 WordPress Randomize Plugin <= 1.4.3 is vulnerable to SQL Injection — Randomize 8.5 High 2024-01-08
CVE-2023-52215 WordPress Barcode Scanner with Inventory & Order Manager Plugin <=1.5.1 is vulnerable to SQL Injection — Simple Inventory Management – just scan barcode to manage products and orders. For WooCommerce 9.3 Critical 2024-01-08
CVE-2024-21747 WordPress WP ERP Plugin <= 1.12.8 is vulnerable to SQL Injection — WP ERP | Complete HR solution with recruitment & job listings | WooCommerce CRM & Accounting 7.6 High 2024-01-08
CVE-2023-6921 SQL Injection in PrestaShop Google Integrator — PrestaShop Google Integrator 9.8 Critical 2024-01-08
CVE-2024-0307 Kashipara Dynamic Lab Management System login_process.php sql injection — Dynamic Lab Management System 7.3 High 2024-01-08
CVE-2024-0306 Kashipara Dynamic Lab Management System admin_login_process.php sql injection — Dynamic Lab Management System 7.3 High 2024-01-08
CVE-2024-0301 fhs-opensource iparking PayTempOrderAction.java getData sql injection — iparking 6.3 Medium 2024-01-08
CVE-2024-0290 Kashipara Food Management System stock_edit.php sql injection — Food Management System 6.3 Medium 2024-01-08
CVE-2024-0289 Kashipara Food Management System stock_entry_submit.php sql injection — Food Management System 6.3 Medium 2024-01-08
CVE-2024-0288 Kashipara Food Management System rawstock_used_damaged_submit.php sql injection — Food Management System 6.3 Medium 2024-01-07
CVE-2024-0287 Kashipara Food Management System itemBillPdf.php sql injection — Food Management System 6.3 Medium 2024-01-07
CVE-2024-0281 Kashipara Food Management System loginCheck.php sql injection — Food Management System 6.3 Medium 2024-01-07
CVE-2024-0280 Kashipara Food Management System item_type_submit.php sql injection — Food Management System 6.3 Medium 2024-01-07
CVE-2024-0279 Kashipara Food Management System item_list_edit.php sql injection — Food Management System 6.3 Medium 2024-01-07
CVE-2024-0278 Kashipara Food Management System partylist_edit_submit.php sql injection — Food Management System 6.3 Medium 2024-01-07
CVE-2024-0277 Kashipara Food Management System party_submit.php sql injection — Food Management System 6.3 Medium 2024-01-07
CVE-2024-0276 Kashipara Food Management System rawstock_used_damaged_smt.php sql injection — Food Management System 6.3 Medium 2024-01-07
CVE-2024-0275 Kashipara Food Management System item_edit_submit.php sql injection — Food Management System 6.3 Medium 2024-01-07
CVE-2024-0274 Kashipara Food Management System billAjax.php sql injection — Food Management System 6.3 Medium 2024-01-07
CVE-2024-0273 Kashipara Food Management System addwaste_entry.php sql injection — Food Management System 6.3 Medium 2024-01-07
CVE-2024-0272 Kashipara Food Management System addmaterialsubmit.php sql injection — Food Management System 6.3 Medium 2024-01-07
CVE-2024-0271 Kashipara Food Management System addmaterial_edit.php sql injection — Food Management System 6.3 Medium 2024-01-07

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