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

Goal: 1000 CNY · Raised: 1336 CNY

100%

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

10280 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-2025-69309 WordPress Saasplate Core plugin <= 1.2.8 - SQL Injection vulnerability — Saasplate Core 9.3 Critical 2026-02-20
CVE-2025-69308 WordPress Nestbyte Core plugin <= 1.2 - SQL Injection vulnerability — Nestbyte Core 9.3 Critical 2026-02-20
CVE-2025-69306 WordPress Electio Core plugin <= 1.4 - SQL Injection vulnerability — Electio Core 9.3 Critical 2026-02-20
CVE-2025-69307 WordPress Medinik Core plugin <= 1.3.6 - SQL Injection vulnerability — Medinik Core 9.3 Critical 2026-02-20
CVE-2025-69305 WordPress Crete Core plugin <= 1.4.3 - SQL Injection vulnerability — Crete Core 9.3 Critical 2026-02-20
CVE-2025-69304 WordPress Allmart plugin <= 1.1 - SQL Injection vulnerability — Allmart 9.3 Critical 2026-02-20
CVE-2025-69295 WordPress Coven Core plugin <= 1.3 - SQL Injection vulnerability — Coven Core 9.3 Critical 2026-02-20
CVE-2025-67987 WordPress Quiz And Survey Master plugin <= 10.3.1 - SQL Injection vulnerability — Quiz And Survey Master 8.5 High 2026-02-20
CVE-2025-10970 SQLi in Kolay Software's Talentics — Talentics 9.8 Critical 2026-02-20
CVE-2026-2822 JeecgBoot Backend airag_app,1,create_by sql injection — JeecgBoot 6.3 Medium 2026-02-20
CVE-2026-2821 Fujian Smart Integrated Management Platform System XCamera.ashx sql injection — Smart Integrated Management Platform System 7.3 High 2026-02-20
CVE-2026-2820 Fujian Smart Integrated Management Platform System XAccessPermissionPlus.ashx sql injection — Smart Integrated Management Platform System 7.3 High 2026-02-20
CVE-2026-26990 LibreNMS has Time-Based Blind SQL Injection in address-search.inc.php — librenms 8.8 High 2026-02-20
CVE-2026-26988 LibreNMS: SQL Injection in ajax_table.php spreads through a covert data stream — librenms 9.8 - 2026-02-20
CVE-2026-26980 Ghost has a SQL Injection in its Content API — Ghost 9.4 Critical 2026-02-20
CVE-2026-2435 ASSET-7706 — Asset 6.3 Medium 2026-02-19
CVE-2026-2409 Delinea Cloud Suite 安全漏洞 — Cloud Suite 9.8AI Critical AI 2026-02-19
CVE-2026-1581 wpForo Forum <= 2.4.14 - Unauthenticated Time-Based SQL Injection — wpForo Forum 7.5 High 2026-02-19
CVE-2026-2232 Product Table and List Builder for WooCommerce Lite <= 4.6.2 - Unauthenticated Time-Based SQL Injection via 'search' Parameter — Product Table and List Builder for WooCommerce Lite 7.5 High 2026-02-19
CVE-2025-15560 SQL Injection in NesterSoft WorkTime — WorkTime (on-prem/cloud) 6.5AI Medium AI 2026-02-19
CVE-2026-25418 WordPress Bit Form plugin <= 2.21.10 - SQL Injection vulnerability — Bit Form 7.6 High 2026-02-19
CVE-2026-25378 WordPress Nelio AB Testing plugin <= 8.2.4 - SQL Injection vulnerability — Nelio AB Testing 7.6 High 2026-02-19
CVE-2026-23805 WordPress Media Search Enhanced plugin <= 0.9.1 - SQL Injection vulnerability — Media Search Enhanced 7.6 High 2026-02-19
CVE-2026-2706 code-projects Patient Record Management System fecalysis_not.php sql injection — Patient Record Management System 6.3 Medium 2026-02-19
CVE-2026-0722 Shield Security <= 21.0.8 - Cross-Site Request Forgery to SQL Injection — Shield: Blocks Bots, Protects Users, and Prevents Security Breaches 6.5 Medium 2026-02-19
CVE-2025-12707 Library Management System <= 3.2.1 - Unauthenticated SQL Injection — Library Management System 7.5 High 2026-02-19
CVE-2026-2691 itsourcecode Event Management System manage_register.php sql injection — Event Management System 7.3 High 2026-02-19
CVE-2026-2690 itsourcecode Event Management System Admin Login ajax.php sql injection — Event Management System 7.3 High 2026-02-19
CVE-2026-2689 itsourcecode Event Management System manage_booking.php sql injection — Event Management System 7.3 High 2026-02-19
CVE-2025-15585 FileFlows 安全漏洞 — fileflows 8.8AI High AI 2026-02-18

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