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

Goal: 1000 CNY · Raised: 1336 CNY

100%

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

10262 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-12487 code-projects Online Class and Exam Scheduling System room_update.php sql injection — Online Class and Exam Scheduling System 6.3 Medium 2024-12-11
CVE-2024-12486 code-projects Online Class and Exam Scheduling System rank_update.php sql injection — Online Class and Exam Scheduling System 6.3 Medium 2024-12-11
CVE-2024-12485 code-projects Online Class and Exam Scheduling System department.php sql injection — Online Class and Exam Scheduling System 6.3 Medium 2024-12-11
CVE-2024-12484 Codezips Technical Discussion Forum signuppost.php sql injection — Technical Discussion Forum 7.3 High 2024-12-11
CVE-2024-12481 cjbi wetech-cms UserDao.java findUser sql injection — wetech-cms 6.3 Medium 2024-12-11
CVE-2024-12480 cjbi wetech-cms TopicDao.java searchTopic sql injection — wetech-cms 6.3 Medium 2024-12-11
CVE-2024-12479 cjbi wetech-cms TopicDao.java searchTopicByKeyword sql injection — wetech-cms 6.3 Medium 2024-12-11
CVE-2024-11773 Ivanti CSA 安全漏洞 — Cloud Services Application 9.1 Critical 2024-12-10
CVE-2024-47977 Dell Avamar SQL注入漏洞 — Avamar 7.1 High 2024-12-10
CVE-2024-47484 Dell Avamar SQL注入漏洞 — Avamar 8.2 High 2024-12-10
CVE-2024-52538 Dell Avamar SQL注入漏洞 — Avamar 7.6 High 2024-12-10
CVE-2024-53947 Apache Superset: Improper SQL authorisation, parse not checking for specific postgres functions — Apache Superset 9.8 - 2024-12-09
CVE-2024-8259 Unauthenticated SQLi in Eryaz IT's NatraCar B2B Dealer Management Program — NatraCar B2B Dealer Management Program 9.8 Critical 2024-12-09
CVE-2024-54215 WordPress Revy plugin <= 1.18 - Unauthenticated SQL Injection vulnerability — Revy 9.3 Critical 2024-12-09
CVE-2024-12360 code-projects Online Class and Exam Scheduling System class_update.php sql injection — Online Class and Exam Scheduling System 6.3 Medium 2024-12-09
CVE-2024-12351 JFinalCMS File Content ContentModel.java findPage sql injection — JFinalCMS 6.3 Medium 2024-12-09
CVE-2024-12270 Beautiful Taxonomy Filters <= 2.4.3 - Unauthenticated SQL Injection — Beautiful taxonomy filters 7.5 High 2024-12-07
CVE-2024-8679 Library Management System <= 3.1 - Authenticated (Admin+) SQL Injection — Library Management System 6.8 Medium 2024-12-07
CVE-2024-50389 QuRouter — QuRouter 9.8 - 2024-12-06
CVE-2024-50387 SMB Service — SMB Service 9.8 - 2024-12-06
CVE-2024-52335 Siemens Healthineers syngo 安全漏洞 — syngo.plaza VB30E 9.8 Critical 2024-12-06
CVE-2024-51615 WordPress WordPress Auction Plugin plugin <= 3.7 - SQL Injection vulnerability — WordPress Auction Plugin 9.3 Critical 2024-12-06
CVE-2024-53807 WordPress WP Mailster plugin <= 1.8.16.0 - SQL Injection vulnerability — WP Mailster 8.5 High 2024-12-06
CVE-2024-53808 WordPress NEX-Forms plugin <= 8.7.8 - SQL Injection vulnerability — NEX-Forms 8.5 High 2024-12-06
CVE-2024-53817 WordPress Acowebs Product Labels For Woocommerce plugin <= 1.5.8 - SQL Injection vulnerability — Product Labels For Woocommerce 7.6 High 2024-12-06
CVE-2024-53815 WordPress Pinpoint Booking System plugin <= 2.9.9.5.2 - SQL Injection vulnerability — Pinpoint Booking System 8.5 High 2024-12-06
CVE-2024-11729 KiviCare – Clinic & Patient Management System (EHR) <= 3.6.4 - Authenticated (Subscriber+) SQL Injection — KiviCare – Clinic & Patient Management System (EHR) 6.5 Medium 2024-12-06
CVE-2024-11730 KiviCare – Clinic & Patient Management System (EHR) <= 3.6.4 - Authenticated (Doctor/Receptionist+) SQL Injection — KiviCare – Clinic & Patient Management System (EHR) 6.5 Medium 2024-12-06
CVE-2024-11460 Verowa Connect <= 3.0.1 - Unauthenticated SQL Injection — Verowa Connect 7.5 High 2024-12-06
CVE-2024-11728 KiviCare – Clinic & Patient Management System (EHR) <= 3.6.4 - Unauthenticated SQL Injection — KiviCare – Clinic & Patient Management System (EHR) 7.5 High 2024-12-06

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