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

Goal: 1000 CNY · Raised: 1325 CNY

100%

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

9545 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-2023-28788 WordPress Advanced Page Visit Counter Plugin <= 6.4.2 is vulnerable to SQL Injection — Advanced Page Visit Counter – Most Wanted Analytics Plugin for WordPress 7.1 High2023-12-20
CVE-2023-29096 WordPress Contact Form to DB by BestWebSoft Plugin <= 1.7.0 is vulnerable to SQL Injection — Contact Form to DB by BestWebSoft – Messages Database Plugin For WordPress 8.5 High2023-12-20
CVE-2023-29432 WordPress Houzez Theme < 2.8.3 is vulnerable to SQL Injection — Houzez - Real Estate WordPress Theme 8.2 High2023-12-20
CVE-2023-30495 WordPress Ultimate Addons for Contact Form 7 Plugin <= 3.1.23 is vulnerable to SQL Injection — Ultimate Addons for Contact Form 7 8.5 High2023-12-20
CVE-2023-30750 WordPress CM Pop-Up banners Plugin <= 1.5.10 is vulnerable to SQL Injection — CM Popup Plugin for WordPress 8.5 High2023-12-20
CVE-2023-30872 WordPress BSK Forms Blacklist Plugin <= 3.6.2 is vulnerable to SQL Injection — BSK Forms Blacklist 7.6 High2023-12-20
CVE-2023-31092 WordPress Easy Bet Plugin <= 1.0.2 is vulnerable to SQL Injection — Easy Bet 5.5 Medium2023-12-20
CVE-2023-32128 WordPress Cryptocurrency Donation Box – Bitcoin & Crypto Donations Plugin <= 2.2.7 is vulnerable to SQL Injection — Cryptocurrency Payment & Donation Box – Accept Payments in any Cryptocurrency on your WP Site for Free 5.5 Medium2023-12-20
CVE-2023-5007 Student Information System v1.0 - Multiple Authenticated SQL Injections (SQLi) — Student Information System 8.8 High2023-12-20
CVE-2023-5011 Student Information System v1.0 - Multiple Authenticated SQL Injections (SQLi) — Student Information System 8.8 High2023-12-20
CVE-2023-32743 WordPress AutomateWoo Plugin <= 5.7.1 is vulnerable to SQL Injection — AutomateWoo 7.6 High2023-12-20
CVE-2023-5010 Student Information System v1.0 - Multiple Authenticated SQL Injections (SQLi) — Student Information System 8.8 High2023-12-20
CVE-2023-33209 WordPress SEO Change Monitor Plugin <= 1.2 is vulnerable to SQL Injection — SEO Change Monitor – Track Website Changes 8.5 High2023-12-20
CVE-2023-33330 WordPress WooCommerce Follow-Up Emails Plugin <= 4.9.50 is vulnerable to SQL Injection — AutomateWoo 8.5 High2023-12-20
CVE-2023-49825 WordPress Soledad Theme <= 8.4.1 is vulnerable to SQL Injection — Soledad – Multipurpose, Newspaper, Blog & WooCommerce WordPress Theme 8.5 High2023-12-20
CVE-2023-49776 WordPress Sayfa Sayaç Plugin <= 2.6 is vulnerable to SQL Injection — Sayfa Sayac 9.3 Critical2023-12-20
CVE-2023-35915 WordPress WooCommerce Payments Plugin <= 5.9.0 is vulnerable to SQL Injection — WooPayments – Fully Integrated Solution Built and Supported by Woo 7.6 High2023-12-20
CVE-2023-40010 WordPress HUSKY – Products Filter for WooCommerce (formerly WOOF) Plugin <= 1.3.4.2 is vulnerable to SQL Injection — HUSKY – Products Filter for WooCommerce Professional 9.3 Critical2023-12-20
CVE-2023-32590 WordPress Subscribe to Category Plugin <= 2.7.4 is vulnerable to SQL Injection — Subscribe to Category 9.3 Critical2023-12-20
CVE-2023-47852 WordPress Link Whisper Free Plugin <= 0.6.5 is vulnerable to SQL Injection — Link Whisper Free 8.5 High2023-12-20
CVE-2023-38519 WordPress MainWP Plugin <= 4.4.3.3 is vulnerable to SQL Injection — MainWP Dashboard – WordPress Manager for Multiple Websites Maintenance 7.6 High2023-12-20
CVE-2023-47236 WordPress iPages Flipbook Plugin <= 1.4.8 is vulnerable to SQL Injection — iPages Flipbook For WordPress 7.6 High2023-12-20
CVE-2023-48327 WordPress WC Vendors Marketplace Plugin <= 2.4.7 is vulnerable to SQL Injection — WC Vendors – WooCommerce Multi-Vendor, WooCommerce Marketplace, Product Vendors 7.6 High2023-12-19
CVE-2023-48738 WordPress Porto Theme - Functionality Plugin < 2.12.1 is vulnerable to SQL Injection — Porto Theme - Functionality 9.3 Critical2023-12-19
CVE-2023-48741 WordPress ChatBot Plugin <= 4.7.8 is vulnerable to SQL Injection — AI ChatBot 7.6 High2023-12-19
CVE-2023-48764 WordPress WordPress Brute Force Protection – Stop Brute Force Attacks Plugin <= 2.2.5 is vulnerable to SQL Injection — WordPress Brute Force Protection – Stop Brute Force Attacks 7.6 High2023-12-19
CVE-2023-49750 WordPress Couponis Demo Plugin < 2.2 is vulnerable to SQL Injection — Couponis - Affiliate & Submitting Coupons WordPress Theme 9.3 Critical2023-12-19
CVE-2023-49764 WordPress Advanced Database Cleaner Plugin <= 3.1.2 is vulnerable to SQL Injection — Advanced Database Cleaner 7.6 High2023-12-19
CVE-2023-49736 Apache Superset: SQL Injection on where_in JINJA macro — Apache Superset 6.5 Medium2023-12-19
CVE-2023-47506 WordPress Master Slider Pro Plugin <= 3.6.5 is vulnerable to SQL Injection — Master Slider Pro 7.6 High2023-12-18

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