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-5709 WD WidgetTwitter <= 1.0.9 - Authenticated (Contributor+) SQL Injection via Shortcode — WD WidgetTwitter 8.8 High 2023-11-07
CVE-2023-46823 WordPress ImageLinks Interactive Image Builder Plugin <= 1.5.4 is vulnerable to SQL Injection — ImageLinks Interactive Image Builder for WordPress 7.6 High 2023-11-06
CVE-2023-46821 WordPress GD Security Headers Plugin <= 1.7 is vulnerable to SQL Injection — GD Security Headers 7.6 High 2023-11-06
CVE-2023-46084 WordPress Icons Font Loader Plugin <= 1.1.2 is vulnerable to SQL Injection — Icons Font Loader 8.5 High 2023-11-06
CVE-2023-45830 WordPress Accessibility Suite by Online ADA Plugin <= 4.12 is vulnerable to SQL Injection — Accessibility Suite by Online ADA 8.5 High 2023-11-06
CVE-2023-45657 WordPress Nexter Theme <= 2.0.3 is vulnerable to SQL Injection — Nexter 8.5 High 2023-11-06
CVE-2023-35911 WordPress Contact Form Generator Plugin <= 2.6.0 is vulnerable to SQL Injection — Contact Form Generator : Creative form builder for WordPress 8.5 High 2023-11-06
CVE-2023-45069 WordPress Video Gallery – YouTube Gallery Plugin <= 2.1.3 is vulnerable to SQL Injection — Video Gallery – Best WordPress YouTube Gallery Plugin 7.6 High 2023-11-06
CVE-2023-45074 WordPress Advanced Page Visit Counter Plugin <= 7.1.1 is vulnerable to SQL Injection — Advanced Page Visit Counter – Most Wanted Analytics Plugin for WordPress 8.5 High 2023-11-06
CVE-2023-45055 WordPress MStore API Plugin <= 4.0.6 is vulnerable to SQL Injection — MStore API 8.5 High 2023-11-06
CVE-2023-28748 WordPress Copy Or Move Comments Plugin <= 5.0.4 is vulnerable to SQL Injection — Copy or Move Comments 8.5 High 2023-11-06
CVE-2023-45046 WordPress Pressference Exporter Plugin <= 1.0.3 is vulnerable to SQL Injection — Pressference Exporter 5.5 Medium 2023-11-06
CVE-2023-45001 WordPress Seriously Simple Stats Plugin <= 1.5.0 is vulnerable to SQL Injection — Seriously Simple Stats 8.5 High 2023-11-06
CVE-2023-41685 WordPress Woocommerce Support System Plugin <= 1.2.1 is vulnerable to SQL Injection — Woocommerce Support System 7.6 High 2023-11-06
CVE-2023-40609 WordPress Contact form 7 Custom validation Plugin <= 1.1.3 is vulnerable to SQL Injection — Contact form 7 Custom validation 8.2 High 2023-11-06
CVE-2023-27605 WordPress WP Reroute Email Plugin <= 1.4.6 is vulnerable to SQL Injection — WP Reroute Email 5.5 Medium 2023-11-06
CVE-2023-33924 WordPress SIS Handball Plugin <= 1.0.45 is vulnerable to SQL Injection — SIS Handball 7.6 High 2023-11-06
CVE-2023-38382 WordPress Subscribe to Category Plugin <= 2.7.4 is vulnerable to SQL Injection — Subscribe to Category 9.8 - 2023-11-06
CVE-2023-40207 WordPress Donations Made Easy – Smart Donations Plugin <= 4.0.12 is vulnerable to SQL Injection — Donations Made Easy – Smart Donations 7.6 High 2023-11-06
CVE-2022-46849 WordPress Coming Soon Plugin <= 1.5.9 is vulnerable to SQL Injection — Coming Soon Page – Responsive Coming Soon & Maintenance Mode 7.6 High 2023-11-06
CVE-2022-46860 WordPress Short URL Plugin <= 1.6.4 is vulnerable to SQL Injection — Short URL 8.5 High 2023-11-06
CVE-2022-45373 WordPress Slimstat Analytics Plugin <= 5.0.4 is vulnerable to SQL Injection — Slimstat Analytics 8.8 High 2023-11-06
CVE-2022-47432 WordPress Shortcode IMDB Plugin <= 6.0.8 is vulnerable to SQL Injection — Shortcode IMDB 6.7 Medium 2023-11-06
CVE-2022-47430 WordPress The School Management – Education & Learning Management Plugin <= 4.1 is vulnerable to SQL Injection — The School Management – Education & Learning Management 6.7 Medium 2023-11-06
CVE-2022-47420 WordPress Accessibility Suite by Online ADA Plugin <= 4.12 is vulnerable to SQL Injection — Accessibility Suite by Online ADA 6.4 Medium 2023-11-06
CVE-2022-47428 WordPress Booking calendar, Appointment Booking System Plugin <= 3.2.7 is vulnerable to SQL Injection — Booking calendar, Appointment Booking System 6.7 Medium 2023-11-06
CVE-2023-40215 WordPress Demon image annotation Plugin <= 5.1 is vulnerable to SQL Injection — demon image annotation 7.6 High 2023-11-03
CVE-2023-35910 WordPress Quasar form Plugin <= 6.0 is vulnerable to SQL Injection — Quasar form free – Contact Form Builder for WordPress 8.5 High 2023-11-03
CVE-2023-38391 WordPress Onepage Builder – Easiest Landing Page Builder For WordPress Plugin <= 2.4.1 is vulnerable to SQL Injection — Onepage Builder 6.7 Medium 2023-11-03
CVE-2023-32741 WordPress Contact Form to Any API Plugin <= 1.1.2 is vulnerable to SQL Injection — Contact Form to Any API 7.6 High 2023-11-03

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