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

Goal: 1000 CNY · Raised: 1336 CNY

100%

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

9995 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, AvailabilityExecute 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.
ConfidentialityRead Application Data
Since SQL databases generally hold sensitive data, loss of confidentiality is a frequent problem with SQL injection vulnerabilities.
AuthenticationGain 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 ControlBypass 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.
IntegrityModify 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 DesignUse 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 DesignIf 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, OperationRun 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 DesignFor 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.
ImplementationWhile 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 IDTitleCVSSSeverityPublished
CVE-2025-0214 TMD Custom Header Menu index.php sql injection — Custom Header Menu 4.1 Medium2025-01-04
CVE-2025-0212 Campcodes Student Grading System view_students.php sql injection — Student Grading System 6.3 Medium2025-01-04
CVE-2024-41767 IBM Engineering Lifecycle Optimization - Publishing SQL injection — Engineering Lifecycle Optimization Publishing 7.3 High2025-01-04
CVE-2025-0210 Campcodes School Faculty Scheduling System ajax.php sql injection — School Faculty Scheduling System 7.3 High2025-01-04
CVE-2025-0208 code-projects Online Shoe Store summary.php sql injection — Online Shoe Store 6.3 Medium2025-01-04
CVE-2025-0207 code-projects Online Shoe Store login.php sql injection — Online Shoe Store 7.3 High2025-01-04
CVE-2024-12195 WP Project Manager – Task, team, and project management plugin featuring kanban board and gantt charts <= 2.6.16 - Authenticated (Subscriber+) SQL Injection — Project Manager – AI Powered Project Management, Task Management, Kanban Board & Time Tracker 6.5 Medium2025-01-04
CVE-2025-0205 code-projects Online Shoe Store details2.php sql injection — Online Shoe Store 6.3 Medium2025-01-04
CVE-2025-0204 code-projects Online Shoe Store details.php sql injection — Online Shoe Store 6.3 Medium2025-01-04
CVE-2025-0203 code-projects Student Management System DbFunction.php showSubject1 sql injection — Student Management System 6.3 Medium2025-01-04
CVE-2025-0201 code-projects Point of Sales and Inventory Management System update_account.php sql injection — Point of Sales and Inventory Management System 6.3 Medium2025-01-04
CVE-2025-0200 code-projects Point of Sales and Inventory Management System search_num.php sql injection — Point of Sales and Inventory Management System 6.3 Medium2025-01-04
CVE-2025-0199 code-projects Point of Sales and Inventory Management System minus_cart.php sql injection — Point of Sales and Inventory Management System 6.3 Medium2025-01-03
CVE-2025-0198 code-projects Point of Sales and Inventory Management System search_result.php sql injection — Point of Sales and Inventory Management System 6.3 Medium2025-01-03
CVE-2025-0197 code-projects Point of Sales and Inventory Management System search.php sql injection — Point of Sales and Inventory Management System 6.3 Medium2025-01-03
CVE-2025-0196 code-projects Point of Sales and Inventory Management System plist.php sql injection — Point of Sales and Inventory Management System 6.3 Medium2025-01-03
CVE-2025-0195 code-projects Point of Sales and Inventory Management System del_product.php sql injection — Point of Sales and Inventory Management System 6.3 Medium2025-01-03
CVE-2025-0176 code-projects Point of Sales and Inventory Management System add_cart.php sql injection — Point of Sales and Inventory Management System 6.3 Medium2025-01-03
CVE-2025-0174 code-projects Point of Sales and Inventory Management System Parameter search_result2.php sql injection — Point of Sales and Inventory Management System 6.3 Medium2025-01-03
CVE-2025-0173 SourceCodester Online Eyewear Shop view_order.php sql injection — Online Eyewear Shop 6.3 Medium2025-01-02
CVE-2025-0172 code-projects Chat System deleteroom.php sql injection — Chat System 6.3 Medium2025-01-02
CVE-2025-0171 code-projects Chat System deleteuser.php sql injection — Chat System 6.3 Medium2025-01-02
CVE-2024-56250 WordPress Just Writing Statistics plugin <= 4.7 - SQL Injection vulnerability — Just Writing Statistics 7.6 High2025-01-02
CVE-2024-56247 WordPress WP Post Author plugin <= 3.8.2 - SQL Injection vulnerability — WP Post Author 7.6 High2025-01-02
CVE-2024-13093 code-projects Job Recruitment Seeker Profile _call_main_search_ajax.php sql injection — Job Recruitment 6.3 Medium2025-01-02
CVE-2024-13092 code-projects Job Recruitment Job Post search_ajax.php sql injection — Job Recruitment 6.3 Medium2025-01-02
CVE-2025-22214 Landray EIS 安全漏洞 — n/a 4.3 Medium2025-01-02
CVE-2025-0168 code-projects Job Recruitment _feedback_system.php sql injection — Job Recruitment 6.3 Medium2025-01-01
CVE-2024-13085 PHPGurukul Land Record System login.php sql injection — Land Record System 7.3 High2024-12-31
CVE-2024-13084 PHPGurukul Land Record System search-property.php sql injection — Land Record System 6.3 Medium2024-12-31

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