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-2026-1472 Out-of-band SQL injection in Quatuor Performance Evaluation — Evaluación de Desempeño (EDD) 7.5AIHighAI2026-01-27
CVE-2021-47902 Testa Online Test Management System 3.4.7 - 'q' SQL Injection — Testa Online Test Management System 8.2 High2026-01-27
CVE-2020-36951 Phpscript-sgh 0.1.0 - Time Based Blind SQL Injection — phpscript-sgh 8.2 High2026-01-27
CVE-2020-36947 LibreNMS 1.46 - MAC Accounting Graph Authenticated SQL Injection — LibreNMS 7.1 High2026-01-27
CVE-2026-1449 Hisense TransTech Smart Bus Management System TireMng.aspx Page_Load sql injection — Smart Bus Management System 7.3 High2026-01-26
CVE-2026-1443 code-projects Online Music Site AdminDeleteUser.php sql injection — Online Music Site 7.3 High2026-01-26
CVE-2026-1422 code-projects Online Examination System Login Page index.php sql injection — Online Examination System 7.3 High2026-01-26
CVE-2026-0806 WP-ClanWars <= 2.0.1 - Authenticated (Administrator+) SQL Injection via 'orderby' Parameter — WP-ClanWars 4.9 Medium2026-01-24
CVE-2026-24624 WordPress Neoforum plugin <= 1.0 - SQL Injection vulnerability — Neoforum 7.6 High2026-01-23
CVE-2026-24572 WordPress Nelio Content plugin <= 4.2.0 - SQL Injection vulnerability — Nelio Content 8.5 High2026-01-23
CVE-2026-0603 Org.hibernate/hibernate-core: hibernate: information disclosure and data deletion via second-order sql injection 8.3 High2026-01-23
CVE-2026-24367 WordPress Traveler theme < 3.2.8 - SQL Injection vulnerability — Traveler 8.5 High2026-01-22
CVE-2026-22470 WordPress FireStorm Professional Real Estate plugin <= 2.7.11 - SQL Injection vulnerability — FireStorm Professional Real Estate 7.6 High2026-01-22
CVE-2025-69180 WordPress Ultra Portfolio plugin <= 6.7 - SQL Injection vulnerability — Ultra Portfolio 8.5 High2026-01-22
CVE-2025-69045 WordPress FooEvents for WooCommerce plugin <= 1.20.4 - SQL Injection vulnerability — FooEvents for WooCommerce 8.5 High2026-01-22
CVE-2025-68999 WordPress Happy Addons for Elementor plugin <= 3.20.4 - SQL Injection vulnerability — Happy Addons for Elementor 8.5 High2026-01-22
CVE-2025-68881 WordPress AppExperts plugin <= 1.4.5 - SQL Injection vulnerability — AppExperts 8.5 High2026-01-22
CVE-2025-68857 WordPress Paid Downloads plugin <= 3.15 - SQL Injection vulnerability — Paid Downloads 9.3 Critical2026-01-22
CVE-2025-68034 WordPress CleverReach® WP plugin <= 1.5.21 - SQL Injection vulnerability — CleverReach® WP 9.3 Critical2026-01-22
CVE-2025-68017 WordPress Antideo Email Validator plugin <= 1.0.10 - SQL Injection vulnerability — Antideo Email Validator 7.5 High2026-01-22
CVE-2025-67945 WordPress MailerLite – WooCommerce integration plugin <= 3.1.2 - SQL Injection vulnerability — MailerLite – WooCommerce integration 9.3 Critical2026-01-22
CVE-2025-49055 WordPress WP Lead Capturing Pages plugin <= 2.5 - SQL Injection vulnerability — WP Lead Capturing Pages 9.3 Critical2026-01-22
CVE-2025-49049 WordPress DZS Video Gallery plugin <= 12.39 - SQL Injection vulnerability — DZS Video Gallery 8.5 High2026-01-22
CVE-2025-49050 WordPress WP Lead Capturing Pages plugin <= 2.5 - SQL Injection vulnerability — WP Lead Capturing Pages 8.5 High2026-01-22
CVE-2025-36588 Dell Unisphere for PowerMax SQL注入漏洞 — Unisphere for PowerMax 8.8 High2026-01-22
CVE-2025-4764 SQLi in Aida Computer's Hotspot — Hotel Guest Hotspot 8.0 High2026-01-22
CVE-2025-27378 SQL Injection in AES Due to Inactive SQL Parsing Configuration — AES 8.6 High2026-01-22
CVE-2021-47872 SEO Panel < 4.9.0 - 'order_col' Blind SQL Injection — SEO Panel 7.1 High2026-01-21
CVE-2021-47848 Blitar Tourism 1.0 - Authentication Bypass SQLi — Aplikasi-Biro-Travel 8.2 High2026-01-21
CVE-2021-47846 Digital Crime Report Management System 1.0 - SQL Injection — Digital Crime Report Management System 8.2 High2026-01-21

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