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-39351 WP Bannerize 2.0.0 - 4.0.2 - Authenticated SQL Injection — WP Bannerize 6.5 -2021-10-06
CVE-2021-24465 Meow Gallery < 4.1.9 - Contributor+ SQL Injection — Meow Gallery (+ Gallery Block) 8.1 -2021-10-04
CVE-2021-36880 WordPress uListing plugin <= 2.0.3 - Unauthenticated SQL Injection (SQLi) vulnerability — uListing (WordPress plugin) 8.6 High2021-09-27
CVE-2021-24666 Podlove Podcast Publisher < 3.5.6 - Unauthenticated SQL Injection — Podlove Podcast Publisher 9.8 -2021-09-27
CVE-2021-24741 Support Board < 3.3.4 - Multiple Unauthenticated SQL Injections — Support Board 9.8 -2021-09-20
CVE-2021-24606 Availability Calendar < 1.2.1 - Authenticated SQL Injection — Availability Calendar 8.8 -2021-09-20
CVE-2021-24511 Create WooCommerce Product Feeds For 40+ Merchants < 3.3.1.0 - Authenticated SQL Injection — Product Feed on WooCommerce for Google, Awin, Shareasale, Bing, and More 7.2 -2021-09-20
CVE-2021-24404 WP-Board <= 1.1 (beta) - Unauthenticated SQL Injection — WP-Board 7.2 -2021-09-20
CVE-2021-24403 WordPress Page Contact <= 1.0 - Authenticated (editor+) SQL Injection — WordPress Page Contact 7.2 -2021-09-20
CVE-2021-24402 WP iCommerce <= 1.1.1 - Authenticated (contributor+) SQL Injection — WP iCommerce – the first interactive ecommerce for wordpress 7.2 -2021-09-20
CVE-2021-24401 WP Domain Redirect <= 1.0 - Authenticated SQL Injection — WP Domain Redirect 7.2 -2021-09-20
CVE-2021-24400 Display users <= 2.0.0 - Authenticated SQL Injection — Display Users 7.2 -2021-09-20
CVE-2021-24399 The Sorter <= 1.0 - Authenticated SQL Injection — The Sorter 7.2 -2021-09-20
CVE-2021-24398 Responsive 3D Slider <= 1.2 - Authenticated SQL Injection — RESPONSIVE 3D SLIDER 7.2 -2021-09-20
CVE-2021-24397 MicroCopy <= 1.1.0 - Authenticated SQL Injection — MicroCopy 7.2 -2021-09-20
CVE-2021-24396 GSEOR <= 1.3 - Authenticated SQL Injection — GSEOR – WordPress SEO Plugin 7.2 -2021-09-20
CVE-2021-33701 SAP ERP SQL注入漏洞 — DMIS Mobile Plug-In 7.2 -2021-09-15
CVE-2021-23040 F5 BIG-IP APM和F5 BIG-IP SQL注入漏洞 — BIG-IP AFM 8.8 -2021-09-14
CVE-2021-24728 Paid Member Subscriptions < 2.4.2 - Authenticated SQL Injection — Membership & Content Restriction – Paid Member Subscriptions 8.8 -2021-09-13
CVE-2021-24727 Block and Stop Bad Bots < 6.60 - Authenticated SQL Injections — WP Block and Stop Bad Bots Crawlers and Spiders and Anti Spam Protection Plugin StopBadBots 8.8 -2021-09-13
CVE-2021-24726 WP Simple Booking Calendar <= 2.0.6 (before 07/12/2021) - Authenticated SQL Injection — WP Simple Booking Calendar 7.2 -2021-09-13
CVE-2021-38324 SP Rental Manager <= 1.5.3 Unauthenticated SQL Injection — SP Rental Manager 8.2 High2021-09-09
CVE-2021-24395 Embed Youtube Video <= 1.0 - Authenticated SQL Injection — Embed Youtube Video 7.2 -2021-09-06
CVE-2021-24393 Comment Highlighter <= 0.13 - Authenticated SQL Injection — Comment Highlighter 7.2 -2021-09-06
CVE-2021-24394 Easy Testimonial Manager <= 1.2.0 - Authenticated SQL Injection — Easy Testimonial Manager 7.2 -2021-09-06
CVE-2021-24392 WordPress Membership SwiftCloud.io <= 1.0 - Authenticated SQL Injection — WordPress Membership SwiftCloud.io 7.2 -2021-09-06
CVE-2021-24391 Cashtomer <= 1.0.0 - Authenticated SQL Injection — Cashtomer 7.2 -2021-09-06
CVE-2021-24390 Alipay <= 3.7.2 - Authenticated SQL Injection — WordPress支付宝Alipay|财付通Tenpay|贝宝PayPal集成插件 7.2 -2021-09-06
CVE-2021-24303 JiangQie Official Website Mini Program < 1.1.1 - Authenticated SQL Injection — JiangQie Official Website Mini Program 7.2 -2021-09-06
CVE-2021-38390 Delta Electronics DIAEnergie SQL注入漏洞 — Delta Electronics DIAEnergie 9.8 -2021-08-30

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