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

Goal: 1000 CNY · Raised: 1336 CNY

100%

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

9995 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-2024-11939 Cost Calculator Builder PRO <= 3.2.15 - Unauthenticated SQL Injection via data — Cost Calculator Builder PRO 7.5 High2025-01-08
CVE-2024-12030 MDTF – Meta Data and Taxonomies Filter <= 1.3.3.5 - Authenticated (Contributor+) SQL Injection — MDTF – Meta Data and Taxonomies Filter 6.5 Medium2025-01-08
CVE-2025-0300 code-projects Online Book Shop subcat.php sql injection — Online Book Shop 6.3 Medium2025-01-07
CVE-2025-22350 WordPress Indeed Ultimate Learning Pro plugin <= 3.9 - SQL Injection vulnerability — Ultimate Learning Pro 7.6 High2025-01-07
CVE-2025-0299 code-projects Online Book Shop search_result.php sql injection — Online Book Shop 6.3 Medium2025-01-07
CVE-2025-0298 code-projects Online Book Shop process_login.php sql injection — Online Book Shop 6.3 Medium2025-01-07
CVE-2025-0297 code-projects Online Book Shop detail.php sql injection — Online Book Shop 6.3 Medium2025-01-07
CVE-2025-22502 WordPress MindValley Super PageMash Plugin <= 1.1 - SQL Injection vulnerability — MindValley Super PageMash 7.6 High2025-01-07
CVE-2025-22507 WordPress WPMU Prefill Post Plugin <= 1.02 - SQL Injection vulnerability — WPMU Prefill Post 7.6 High2025-01-07
CVE-2025-22519 WordPress eDoc Easy Tables Plugin <= 1.29 - SQL Injection vulnerability — eDoc Easy Tables 8.5 High2025-01-07
CVE-2025-22533 WordPress WOOEXIM Plugin <= 5.0.0 - SQL Injection vulnerability — WOOEXIM 7.6 High2025-01-07
CVE-2025-22536 WordPress WP Music Player Plugin <= 1.3 - SQL Injection vulnerability — WP Music Player 7.6 High2025-01-07
CVE-2025-0296 code-projects Online Book Shop booklist.php sql injection — Online Book Shop 6.3 Medium2025-01-07
CVE-2025-0294 SourceCodester Home Clean Services Management System process.php sql injection — Home Clean Services Management System 4.7 Medium2025-01-07
CVE-2024-51715 WordPress ClickWhale plugin <= 2.4.1 - SQL Injection vulnerability — ClickWhale 8.5 High2025-01-07
CVE-2024-56284 WordPress SSL Wireless SMS Notification Plugin <= 3.5.0 - SQL Injection vulnerability — SSL Wireless SMS Notification 9.3 Critical2025-01-07
CVE-2024-56290 WordPress Multiple Shipping And Billing Address For Woocommerce Plugin <= 1.2 - Unauthenticated SQL Injection vulnerability — Multiple Shipping And Billing Address For Woocommerce 9.3 Critical2025-01-07
CVE-2025-22348 WordPress DynamicTags plugin <= 1.4.0 - SQL Injection vulnerability — DynamicTags 8.5 High2025-01-07
CVE-2025-22349 WordPress WordPress Auction Plugin plugin <= 3.7 - SQL Injection vulnerability — WordPress Auction Plugin 7.6 High2025-01-07
CVE-2025-22351 WordPress Contact Form 7 Database – CFDB7 plugin <= 1.0.0 - SQL Injection vulnerability — Contact Form 7 Database – CFDB7 7.6 High2025-01-07
CVE-2025-22352 WordPress ELEX WooCommerce Advanced Bulk Edit Products, Prices & Attributes Plugin <= 1.4.9 - SQL Injection vulnerability — ELEX WooCommerce Advanced Bulk Edit Products, Prices & Attributes 7.6 High2025-01-07
CVE-2024-12332 School Management System – WPSchoolPress <= 2.2.14 - Authenticated (Student/Parent+) SQL Injection — School Management System – WPSchoolPress 6.5 Medium2025-01-07
CVE-2024-12157 Popup – MailChimp, GetResponse and ActiveCampaign Intergrations <= 3.2.6 - Unauthenticated SQL Injection — Popup – MailChimp, GetResponse and ActiveCampaign Intergrations 7.5 High2025-01-07
CVE-2024-12416 Woomotiv <= 3.6.1 - Unauthenticated SQL Injection — Live Sales Notification for Woocommerce – Woomotiv 7.5 High2025-01-07
CVE-2024-11437 Timeline Designer <= 1.4 - Authenticated (Admin+) SQL Injection — Timeline Designer 4.9 Medium2025-01-07
CVE-2025-0233 Codezips Project Management System course.php sql injection — Project Management System 7.3 High2025-01-05
CVE-2025-0232 Codezips Blood Bank Management System successadmin.php sql injection — Blood Bank Management System 6.3 Medium2025-01-05
CVE-2025-0231 Codezips Gym Management System submit_payments.php sql injection — Gym Management System 6.3 Medium2025-01-05
CVE-2025-0230 code-projects Responsive Hotel Site print.php sql injection — Responsive Hotel Site 6.3 Medium2025-01-05
CVE-2025-0229 code-projects Travel Management System enquiry.php sql injection — Travel Management System 6.3 Medium2025-01-05

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