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

Goal: 1000 CNY · Raised: 1000 CNY

100.0%

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

8957 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-2021-24931 Secure Copy Content Protection and Content Locking < 2.8.2 - Unauthenticated SQL Injection — Secure Copy Content Protection and Content Locking 9.8 -2021-12-06
CVE-2021-24866 WP Data Access < 5.0.0 - Admin+ SQL Injection — WP Data Access 9.8 -2021-12-06
CVE-2020-35012 Events Manager < 5.9.8 - Admin+ SQL Injection — Events Manager 7.2 -2021-12-01
CVE-2021-24915 Contest Gallery < 13.1.0.6 - Missing Access Controls to Unauthenticated SQL injection / Email Address Disclosure — Contest Gallery – Photo Contest Plugin for WordPress 9.1 -2021-11-29
CVE-2021-24889 Ninja Forms < 3.6.4 - Admin+ SQL Injection — Ninja Forms Contact Form – The Drag and Drop Form Builder for WordPress 7.2 -2021-11-29
CVE-2021-24860 BSK PDF Manager < 3.1.2 - Admin+ SQL Injection — BSK PDF Manager 7.2 -2021-11-29
CVE-2021-24755 myCred < 2.3 - Subscriber+ SQL Injection — myCred – Points, Rewards, Gamification, Ranks, Badges & Loyalty Plugin 8.8 -2021-11-29
CVE-2021-24748 Email Before Download < 6.8 - Admin+ SQL Injection — Email Before Download 8.8 -2021-11-29
CVE-2021-36916 WordPress Hide My WP premium plugin <= 6.2.3 - Unauthenticated SQL injection (SQLi) vulnerability — Hide My WP (WordPress plugin) 8.6 High2021-11-24
CVE-2021-36300 Dell Emc Idrac SQL注入漏洞 — Integrated Dell Remote Access Controller (iDRAC) 6.5 Medium2021-11-23
CVE-2021-36299 DELL Dell EMC iDRAC9 SQL注入漏洞 — Integrated Dell Remote Access Controller (iDRAC) 7.1 High2021-11-23
CVE-2021-24877 MainWP Child < 4.1.8 - Admin+ SQL Injection — MainWP Child - Securely connects sites to the MainWP WordPress Manager Dashboard 7.2 -2021-11-23
CVE-2021-3935 PgBouncer 信任管理问题漏洞 — pgbouncer 8.1 -2021-11-22
CVE-2021-43408 Duplicate Post WordPress Plugin SQL Injection Vulnerability — Duplicate Post WordPress Plugin 6.5 Medium2021-11-19
CVE-2021-40129 Cisco Common Services Platform Collector SQL Injection Vulnerability — Cisco Common Services Platform Collector Software 4.9 Medium2021-11-18
CVE-2021-24847 SEO Redirection < 8.2 - Subscriber+ SQL Injection — SEO Redirection Plugin – 301 Redirect Manager 8.8 -2021-11-17
CVE-2021-24772 Stream < 3.8.2 - Admin+ SQL Injection — Stream 8.8 -2021-11-17
CVE-2021-24758 Email Log < 2.4.7 - Admin+ SQL Injection — Email Log 8.8 -2021-11-17
CVE-2021-3958 SQL Injection Vulnerability in Ipack SCADA Software — Ipack SCADA Software 9.8 Critical2021-11-16
CVE-2021-24844 Affiliate Manager < 2.8.7 - Admin+ SQL injection — Affiliates Manager 7.2 -2021-11-08
CVE-2021-24835 WCFM - Frontend Manager for WooCommerce < 6.5.12 - Customer/Subscriber+ SQL Injection — WCFM – Frontend Manager for WooCommerce along with Bookings Subscription Listings Compatible 8.8 -2021-11-08
CVE-2021-24829 Visitor Traffic Real Time Statistics < 3.9 - Subscriber+ SQL Injection — Visitor Traffic Real Time Statistics 8.8 -2021-11-08
CVE-2021-24827 Asgaros Forum < 1.15.13 - Unauthenticated SQL Injection — Asgaros Forum 9.8 -2021-11-08
CVE-2021-24791 Header Footer Code Manager < 1.1.14 - Admin+ SQL Injections — Header Footer Code Manager 7.2 -2021-11-08
CVE-2021-24731 Pie Register < 3.7.1.6 - Unauthenticated SQL Injection — Registration Forms – User profile, Content Restriction, Spam Protection, Payment Gateways, Invitation Codes 9.8 -2021-11-08
CVE-2021-24669 MAZ Loader < 1.3.3 - Contributor+ SQL Injection — MAZ Loader – Preloader Builder for WordPress 8.8 -2021-11-08
CVE-2021-24631 Unlimited PopUps <= 4.5.3 - Author+ SQL Injection — Unlimited PopUps 8.8 -2021-11-08
CVE-2021-24630 Schreikasten <= 0.14.18 - Author+ SQL Injections — Schreikasten 8.8 -2021-11-08
CVE-2021-24629 Post Content XMLRPC <= 1.0 - Admin+ SQL Injections — Post Content XMLRPC 7.2 -2021-11-08
CVE-2021-24628 Wow Forms <= 3.1.3 - Admin+ SQL Injection — Wow Forms – create any form with custom style 7.2 -2021-11-08

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