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

Goal: 1000 CNY · Raised: 1336 CNY

100%

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

10254 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-2024-25910 WordPress MoveTo Plugin <= 6.2 is vulnerable to SQL Injection — MoveTo 9.8 Critical 2024-02-28
CVE-2024-25927 WordPress postMash – custom post order Plugin <= 1.2.0 is vulnerable to SQL Injection — postMash – custom post order 9.3 Critical 2024-02-28
CVE-2024-24772 Apache Superset: Improper Neutralisation of custom SQL on embedded context — Apache Superset 4.3 Medium 2024-02-28
CVE-2024-0786 Conversios <= 7.0.7 - Authenticated (Subscriber+) SQL Injection via ee_syncProductCategory — Conversios: Google Analytics (GA4), Google Ads, Conversion and Analytics Tracking for Multi-Channels 8.8 High 2024-02-28
CVE-2024-1514 WP eCommerce <= 3.15.1 - Unauthenticated SQL Injection — WP eCommerce 9.8 Critical 2024-02-28
CVE-2024-1928 SourceCodester Web-Based Student Clearance System Edit User Profile Page edit-admin.php sql injection — Web-Based Student Clearance System 4.7 Medium 2024-02-27
CVE-2024-1927 SourceCodester Web-Based Student Clearance System login.php sql injection — Web-Based Student Clearance System 6.3 Medium 2024-02-27
CVE-2024-1926 SourceCodester Free and Open Source Inventory Management System search_sales_report.php sql injection — Free and Open Source Inventory Management System 6.3 Medium 2024-02-27
CVE-2024-1924 CodeAstro Membership Management System get_membership_amount.php sql injection — Membership Management System 6.3 Medium 2024-02-27
CVE-2024-1923 SourceCodester Simple Student Attendance System List of Classes Page ajax-api.php delete_student sql injection — Simple Student Attendance System 6.3 Medium 2024-02-27
CVE-2024-1698 NotificationX – Best FOMO, Social Proof, WooCommerce Sales Popup & Notification Bar Plugin With Elementor <= 2.8.2 - Unauthenticated SQL Injection — NotificationX – FOMO, Live Sales Notification, WooCommerce Sales Popup, GDPR, Social Proof, Announcement Banner & Floating Notification Bar 9.8 Critical 2024-02-27
CVE-2024-1878 SourceCodester Employee Management System myprofile.php sql injection — Employee Management System 6.3 Medium 2024-02-26
CVE-2024-1877 SourceCodester Employee Management System cancel.php sql injection — Employee Management System 6.3 Medium 2024-02-26
CVE-2024-1876 SourceCodester Employee Management System psubmit.php sql injection — Employee Management System 7.3 High 2024-02-26
CVE-2024-1833 SourceCodester Employee Management System login.php sql injection — Employee Management System 7.3 High 2024-02-23
CVE-2024-1832 SourceCodester Complete File Management System Admin Login Form sql injection — Complete File Management System 7.3 High 2024-02-23
CVE-2024-1831 SourceCodester Complete File Management System Login Form index.php sql injection — Complete File Management System 7.3 High 2024-02-23
CVE-2022-43842 IBM Aspera Console SQL injection — Aspera Console 8.6 High 2024-02-23
CVE-2024-1830 code-projects Library System lost-password.php sql injection — Library System 7.3 High 2024-02-23
CVE-2024-1829 code-projects Library System registration.php sql injection — Library System 7.3 High 2024-02-23
CVE-2024-1828 code-projects Library System registration.php sql injection — Library System 7.3 High 2024-02-23
CVE-2024-1827 code-projects Library System login.php sql injection — Library System 7.3 High 2024-02-23
CVE-2024-1826 code-projects Library System login.php sql injection — Library System 7.3 High 2024-02-23
CVE-2024-1824 CodeAstro House Rental Management System signing.php sql injection — House Rental Management System 7.3 High 2024-02-23
CVE-2024-1821 code-projects Crime Reporting System police_add.php sql injection — Crime Reporting System 5.5 Medium 2024-02-23
CVE-2024-1820 code-projects Crime Reporting System inchargelogin.php sql injection — Crime Reporting System 7.3 High 2024-02-23
CVE-2024-25928 WordPress Sitepact's Contact Form 7 Extension For Klaviyo Plugin <= 1.0.5 is vulnerable to SQL Injection — Sitepact 7.1 High 2024-02-23
CVE-2024-1776 Admin side data storage for Contact Form 7 <= 1.1.1 - Authenticated (Admin+) SQL Injection — Admin side data storage for Contact Form 7 7.2 High 2024-02-23
CVE-2024-1784 Limbas main_admin.php sql injection — Limbas 3.9 Low 2024-02-23
CVE-2024-1702 keerti1924 PHP-MYSQL-User-Login-System edit.php sql injection — PHP-MYSQL-User-Login-System 6.3 Medium 2024-02-21

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