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

Goal: 1000 CNY · Raised: 1359 CNY

100%

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

10891 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-105889 WordPress Tickera plugin <= 3.6.0.6 - SQL Injection vulnerability — Tickera 9.3 Critical 2026-10-10
CVE-2026-96653 WP Directory Kit <= 1.5.9 - Authenticated (Subscriber+) SQL Injection via 'display_name' Profile Field (Second-Order) — WP Directory Kit 6.5 Medium 2026-10-10
CVE-2026-96662 Appointment Booking Plugin <= 5.7.2 - Unauthenticated SQL Injection via 'booking[service_id]' Parameter — Appointment Booking Plugin – LatePoint | Calendar & Scheduling for WordPress 7.5 High 2026-10-10
CVE-2026-107712 WP Booking System <= 2.1.0.1 - Authenticated (Subscriber+) SQL Injection via 'current_month' Parameter — WP Booking System – Booking Calendar 6.5 Medium 2026-10-10
CVE-2026-104023 Smart Popup by Supsystic <= 1.13.2 - Authenticated (Administrator+) SQL Injection via 'sidx' Parameter — Smart Popup by Supsystic 4.9 Medium 2026-10-10
CVE-2026-104724 FireBox <= 3.1.13 - Authenticated (Author+) SQL Injection via FireBox Form Display Condition — FireBox – WooCommerce Popup Builder, Exit Intent Popup, Email Optin & Cart Abandonment 5.3 Medium 2026-10-10
CVE-2026-108474 JetBrains Exposed <1.5.1 SQL注入漏洞 — Exposed 9.8 Critical 2026-10-09
CVE-2026-108125 WordPress Post Author Authenticated SQLi 7.1 High 2026-10-09
CVE-2026-108124 WordPress Post Author Authenticated SQLi 4.9 Medium 2026-10-09
CVE-2026-108107 PHPNuxBill through 2025.3.20 Unauthenticated SQL Injection via radius.php — phpnuxbill 9.8 Critical 2026-10-09
CVE-2026-108100 HortusFox before 6.2 SQL Injection via /api/locations/list include_info Parameter — hortusfox-web 6.5 Medium 2026-10-09
CVE-2026-107803 ProcessMaker has SQL injection in the tasks endpoint through the order_by parameter — processmaker 6.5 Medium 2026-10-09
CVE-2026-93947 WordPress Traveler theme <= 3.2.9 - SQL Injection vulnerability — Traveler 9.3 Critical 2026-10-09
CVE-2026-94663 WordPress ProfileGrid plugin <= 6.0.0.2 - SQL Injection vulnerability — ProfileGrid 8.5 High 2026-10-09
CVE-2026-96809 WordPress EduAdmin Booking plugin < 6.0.0 - SQL Injection vulnerability — EduAdmin Booking 9.3 Critical 2026-10-09
CVE-2026-96329 WordPress tagDiv Opt-In Builder plugin <= 1.7.6 - SQL Injection vulnerability — tagDiv Opt-In Builder 8.5 High 2026-10-09
CVE-2026-96328 WordPress JNews - Pay Writer plugin <= 12.0.1 - SQL Injection vulnerability — JNews - Pay Writer 9.3 Critical 2026-10-09
CVE-2026-96331 WordPress Ajax Search Pro plugin <= 4.29.1 - SQL Injection vulnerability — Ajax Search Pro 9.3 Critical 2026-10-09
CVE-2026-96330 WordPress tagDiv Opt-In Builder plugin <= 1.7.6 - SQL Injection vulnerability — tagDiv Opt-In Builder 9.3 Critical 2026-10-09
CVE-2026-95599 WordPress Taskbuilder plugin <= 6.0.5 - SQL Injection vulnerability — Taskbuilder 8.5 High 2026-10-09
CVE-2026-95607 WordPress WPLMS theme <= 4.973 - SQL Injection vulnerability — WPLMS 8.5 High 2026-10-09
CVE-2026-96327 WordPress WPLMS plugin < 1.9.9.8.2 - SQL Injection vulnerability — WPLMS 9.3 Critical 2026-10-09
CVE-2026-95610 WordPress UpSolution Core plugin <= 9.3 - SQL Injection vulnerability — UpSolution Core 8.5 High 2026-10-09
CVE-2025-71428 Jivejdon through 5.0 SQL Injection via username in userListAction — jivejdon 4.9 Medium 2026-10-08
CVE-2026-80381 Multiple vulnerabilities affect the Sniffer component as part of IBM Guardium Data Protection — Guardium Data Protection 9.8 Critical 2026-10-08
CVE-2026-81932 Multiple vulnerabilities affect the Sniffer component as part of IBM Guardium Data Protection — Guardium Data Protection 8.6 High 2026-10-08
CVE-2026-84209 IBM Guardium Data Protection is affected by multiple vulnerabilities. — Guardium Data Protection 8.1 High 2026-10-08
CVE-2026-16830 Security vulnerabilities have been found in IBM Verify Identity Access and IBM Security Verify Access — Security Verify Access 5.4 Medium 2026-10-08
CVE-2026-107385 MariaDB Connector/Node.js: SQL injection in the text protocol when the session uses NO_BACKSLASH_ESCAPES — mariadb-connector-nodejs 7.4 High 2026-10-08
CVE-2026-107384 MariaDB Connector/Node.js: SQL injection through object keys in SET expansion (permitSetMultiParamEntries) — mariadb-connector-nodejs 8.1 High 2026-10-08

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