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

Goal: 1000 CNY · Raised: 1336 CNY

100%

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

10268 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-2026-44047 SQL injection in MySQL CNID backend — Netatalk 8.8 High 2026-05-21
CVE-2026-9082 Drupal core - Highly critical - SQL injection - SA-CORE-2026-004 — Drupal core 9.8 Critical 2026-05-20
CVE-2026-42383 WordPress YITH WooCommerce Product Add-Ons plugin <= 4.29.0 - SQL Injection vulnerability — YITH WooCommerce Product Add-Ons 7.6 High 2026-05-20
CVE-2026-9065 Surecart - SQL Injection — Surecart - - 2026-05-20
CVE-2026-9059 NextGEN Gallery - SQL Injection — NextGEN Gallery - - 2026-05-20
CVE-2026-9003 TONNET|E-LAN Hybrid Recording System - SQL Injection — TPR7308 7.5 High 2026-05-20
CVE-2026-9010 Boost <= 2.0.3 - Unauthenticated Blind SQL Injection via Multiple Parameters — Boost 7.5 High 2026-05-20
CVE-2026-7472 Read More & Accordion <= 3.5.7 - Authenticated (Administrator+) SQL Injection via 'orderby' Parameter — Read More & Accordion 4.9 Medium 2026-05-20
CVE-2026-3985 Creative Mail – Easier WordPress & WooCommerce Email Marketing <= 1.6.9 - Unauthenticated SQL Injection via 'checkout_uuid' Parameter — Creative Mail – Easier WordPress & WooCommerce Email Marketing 7.5 High 2026-05-20
CVE-2026-8685 Infility Global <= 2.15.16 - Authenticated (Subscriber+) SQL Injection via 'orderby' Parameter — Infility Global 6.5 Medium 2026-05-20
CVE-2026-8912 Contest Gallery <= 28.1.6 - Unauthenticated SQL Injection — Contest Gallery – Upload & Vote Photos, Media, Sell with PayPal & Stripe 7.5 High 2026-05-19
CVE-2026-8827 SQL Injection in extension "Address List" (tt_address) — Extension "Address List" - - 2026-05-19
CVE-2026-8726 SQL Injection in extension "News system" (news) — Extension "News system" - - 2026-05-19
CVE-2026-8851 SOGo < 5.12.8 SQL Injection via addUserInAcls endpoint — SOGo Webmail 8.1 High 2026-05-18
CVE-2026-8785 projectworlds hospital-management-system-in-php GET Parameter update_info.php getAllPatientDetail sql injection — hospital-management-system-in-php 7.3 High 2026-05-18
CVE-2026-8772 linlinjava litemall Admin Endpoint sql injection — litemall 4.7 Medium 2026-05-17
CVE-2026-8771 linlinjava litemall Front-end WeChat API WxGoodsController.java list sql injection — litemall 7.3 High 2026-05-17
CVE-2018-25339 Zechat 1.5 SQL Injection via v parameter (time-based blind) — Zechat 8.2 High 2026-05-17
CVE-2018-25338 Zechat 1.5 SQL Injection via hashtag parameter — Zechat 8.2 High 2026-05-17
CVE-2018-25333 Nordex N149/4.0-4.5 Wind Turbine Web Server SQL Injection — N149 Wind Turbine Web Server 8.2 High 2026-05-17
CVE-2018-25330 Joomla! EkRishta 2.10 Persistent XSS and SQL Injection — Joomla! extension EkRishta 8.2 High 2026-05-17
CVE-2018-25319 Redaxo CMS Addon MyEvents 2.2.1 SQL Injection via event_add.php — Redaxo CMS Addon MyEvents 7.1 High 2026-05-17
CVE-2026-8734 Oinone Pamirs queryListByWrapper RSQLToSQLNodeConnector.makeVariable sql injection — Pamirs 7.3 High 2026-05-17
CVE-2026-8724 Dataease Data Dashboard SqlparserUtils.java SqlparserUtils.transFilter sql injection — Dataease 4.7 Medium 2026-05-17
CVE-2021-47980 Fuel CMS 1.4.13 Blind SQL Injection via col Parameter — Fuel CMS 7.1 High 2026-05-16
CVE-2021-47956 EgavilanMedia PHPCRUD 1.0 SQL Injection via firstname — EgavilanMedia PHPCRUD 8.2 High 2026-05-16
CVE-2021-47954 LayerBB 1.1.4 SQL Injection via search_query Parameter — LayerBB 8.2 High 2026-05-16
CVE-2020-37243 WordPress Plugin Supsystic Pricing Table 1.8.7 SQL Injection XSS — Pricing Table 8.2 High 2026-05-16
CVE-2020-37244 WordPress Plugin Supsystic Membership 1.4.7 SQL Injection via sidx — Membership 8.2 High 2026-05-16
CVE-2020-37242 WordPress Plugin Supsystic Ultimate Maps 1.1.12 SQL Injection via sidx — Ultimate Maps 8.2 High 2026-05-16

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