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-2023-44088 SQL Injection in Visual Console — Pandora FMS 5.9 Medium 2023-12-29
CVE-2023-50837 WordPress Login Lockdown Plugin <= 2.06 is vulnerable to SQL Injection — Login Lockdown – Protect Login Form 7.6 High 2023-12-29
CVE-2023-52135 WordPress WS Form LITE Plugin <= 1.9.170 is vulnerable to SQL Injection — WS Form LITE – Drag & Drop Contact Form Builder for WordPress 7.6 High 2023-12-29
CVE-2023-7161 Netentsec NS-ASG Application Security Gateway Login sql injection — NS-ASG Application Security Gateway 7.3 High 2023-12-29
CVE-2023-7157 SourceCodester Free and Open Source Inventory Management System sell_return_data.php sql injection — Free and Open Source Inventory Management System 6.3 Medium 2023-12-29
CVE-2023-7156 Campcodes Online College Library System Search index.php sql injection — Online College Library System 7.3 High 2023-12-29
CVE-2023-7155 SourceCodester Free and Open Source Inventory Management System edit_product.php sql injection — Free and Open Source Inventory Management System 6.3 Medium 2023-12-29
CVE-2023-7146 gopeak MasterLab HTTP POST Request Feature.php sqlInjectDelete sql injection — MasterLab 6.3 Medium 2023-12-29
CVE-2023-7145 gopeak MasterLab HTTP POST Request Framework.php sqlInject sql injection — MasterLab 6.3 Medium 2023-12-29
CVE-2023-7144 gopeak MasterLab HTTP POST Request Feature.php sqlInject sql injection — MasterLab 6.3 Medium 2023-12-29
CVE-2023-7142 code-projects Client Details System clientview.php sql injection — Client Details System 4.3 Medium 2023-12-29
CVE-2023-7141 code-projects Client Details System update-clients.php sql injection — Client Details System 4.3 Medium 2023-12-28
CVE-2023-7140 code-projects Client Details System manage-users.php sql injection — Client Details System 4.3 Medium 2023-12-28
CVE-2023-7139 code-projects Client Details System HTTP POST Request regester.php sql injection — Client Details System 4.3 Medium 2023-12-28
CVE-2023-7138 code-projects Client Details System HTTP POST Request admin sql injection — Client Details System 6.3 Medium 2023-12-28
CVE-2023-7137 code-projects Client Details System HTTP POST Request sql injection — Client Details System 6.3 Medium 2023-12-28
CVE-2023-50838 WordPress NEX-Forms – Ultimate Form Builder Plugin <= 8.5.5 is vulnerable to SQL Injection — NEX-Forms – Ultimate Form Builder – Contact forms and much more 7.6 High 2023-12-28
CVE-2023-50839 WordPress JS Help Desk – Best Help Desk & Support Plugin <= 2.8.1 is vulnerable to SQL Injection — JS Help Desk – Best Help Desk & Support Plugin 9.3 Critical 2023-12-28
CVE-2023-50840 WordPress Booking Manager Plugin <= 2.1.5 is vulnerable to SQL Injection — Booking Manager 8.5 High 2023-12-28
CVE-2023-50841 WordPress BookingPress Plugin <= 1.0.72 is vulnerable to SQL Injection — BookingPress – Appointment Booking Calendar Plugin and Online Scheduling Plugin 8.5 High 2023-12-28
CVE-2023-50842 WordPress MF Gig Calendar Plugin <= 1.2.1 is vulnerable to SQL Injection — MF Gig Calendar 8.5 High 2023-12-28
CVE-2023-50843 WordPress Clockwork SMS Notfications Plugin <= 3.0.4 is vulnerable to SQL Injection — Clockwork SMS Notfications 7.6 High 2023-12-28
CVE-2023-50844 WordPress WP Mail Catcher Plugin <= 2.1.3 is vulnerable to SQL Injection — Mail logging – WP Mail Catcher 7.6 High 2023-12-28
CVE-2023-50845 WordPress GeoDirectory Plugin <= 2.3.28 is vulnerable to SQL Injection — GeoDirectory – WordPress Business Directory Plugin, or Classified Directory 7.6 High 2023-12-28
CVE-2023-50846 WordPress RegistrationMagic Plugin <= 5.2.4.5 is vulnerable to SQL Injection — RegistrationMagic – Custom Registration Forms, User Registration, Payment, and User Login 7.6 High 2023-12-28
CVE-2023-50847 WordPress Welcart e-Commerce Plugin <= 2.9.3 is vulnerable to SQL Injection — Welcart e-Commerce 7.6 High 2023-12-28
CVE-2023-7131 code-projects Intern Membership Management System User Registration sql injection — Intern Membership Management System 6.3 Medium 2023-12-28
CVE-2023-52082 Lychee is vulnerable to an SQL Injection in explain DB queries. — Lychee 8.8 High 2023-12-28
CVE-2023-7129 code-projects Voting System Voters Login sql injection — Voting System 5.5 Medium 2023-12-28
CVE-2023-7128 code-projects Voting System Admin Login sql injection — Voting System 6.3 Medium 2023-12-28

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