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

Goal: 1000 CNY · Raised: 1359 CNY

100%

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

10995 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-32599 Netmaker has a boolean‑based SQL Injection — netmaker 5.3 Medium 2026-09-15
CVE-2026-81567 Joomla Extension - j2commerce.com - Unauthenticated blind SQL injection in the storefront product list in J2Store 1.0.0-3.3.2, 4.0.0-4.0.22, 4.1.0-4.1.7 — J2Store extension for Joomla 8.7 High 2026-09-15
CVE-2026-61667 DIRAC: RCE in FileCatalog DatasetManager via SQL injection + eval — DIRAC 9.9 Critical 2026-09-15
CVE-2024-58385 Yonyou U8 CRM SQL Injection via fillbacksettingedit.php — U8 CRM 9.8 Critical 2026-09-15
CVE-2026-81895 Concrete CMS 9.5.2 and below is vulnerable to Stored SQL Injection in Concrete CMS Document Library Block via `fsID[]` in `setMode=any` — Concrete CMS 8.5 High 2026-09-15
CVE-2026-81894 Concrete CMS 9.5.2 and below is vulnerable to Stored DOM-based Cross-site Scripting (XSS) in the Gallery block image Caption field — Concrete CMS 8.5 High 2026-09-15
CVE-2026-91848 WuzhiCMS index.php getDataOfJson sql injection — WuzhiCMS 7.3 High 2026-09-15
CVE-2026-91004 SourceCodester Online Faculty Clearance System delete_faculty1.php sql injection — Online Faculty Clearance System 7.3 High 2026-09-15
CVE-2026-90879 zyx0814 FilePress Publish search.php sql injection — FilePress 7.3 High 2026-09-15
CVE-2026-90877 SourceCodester Online Faculty Clearance System update_requirement_status.php sql injection — Online Faculty Clearance System 7.3 High 2026-09-15
CVE-2026-90876 SourceCodester Online Faculty Clearance System delete_requirement.php sql injection — Online Faculty Clearance System 7.3 High 2026-09-15
CVE-2026-90855 SourceCodester/katojkalemba Online Food Ordering System order.php sql injection — Online Food Ordering System 7.3 High 2026-09-15
CVE-2026-90854 SourceCodester/katojkalemba Online Food Ordering System category-foods.php sql injection — Online Food Ordering System 7.3 High 2026-09-15
CVE-2026-90849 SourceCodester College Notes Gallery Management System login.php sql injection — College Notes Gallery Management System 7.3 High 2026-09-15
CVE-2026-90846 PHPGurukul Daily Expense Tracker System forgot-password.php sql injection — Daily Expense Tracker System 7.3 High 2026-09-15
CVE-2026-90844 PHPGurukul Daily Expense Tracker System Login index.php sql injection — Daily Expense Tracker System 7.3 High 2026-09-15
CVE-2026-90841 PHPGurukul Blood Donor Management System Report Endpoint Report.php sql injection — Blood Donor Management System 7.3 High 2026-09-14
CVE-2026-82028 Magistrala < 1.0.0 SQL Injection via format Parameter in Reader API — magistrala 8.8 High 2026-09-14
CVE-2026-90805 subhajitkhan online-clinic-management-system doctorlogin.php sql injection — online-clinic-management-system 7.3 High 2026-09-14
CVE-2026-55416 Pimcore: SQL Injection in Mautic Custom Reports Bundle Due to Direct Concatenation of User-Controlled Configuration Fields Without Parameterization — pimcore 8.8 High 2026-09-14
CVE-2026-76461 Cisco Secure Email Gateway SQL Injection Vulnerability — Cisco Secure Email 9.8 Critical 2026-09-14
CVE-2026-90796 itsourcecode Leave Management System index.php sql injection — Leave Management System 6.3 Medium 2026-09-14
CVE-2026-90789 itsourcecode Leave Management System login.php sql injection — Leave Management System 7.3 High 2026-09-14
CVE-2026-15600 SQL Injection in Alior Bank raty PrestaShop module — raty 8.6 High 2026-09-14
CVE-2026-7848 SQL Injection in Alior Bank raty PrestaShop module — raty 8.6 High 2026-09-14
CVE-2026-77051 Apache Syncope: SQL injection via unsanitized entityKey and opEvent in Audit Events search — Apache Syncope - - 2026-09-14
CVE-2026-90708 Yot CMS Cookie global.php login sql injection — CMS 7.3 High 2026-09-14
CVE-2026-78375 Joomla Extension - joomshaper.com - Authenticated Privileged SQL Injection in the Content Plugin of SP Page Builder (Free and Pro) 5.2.1 - 6.9.0 — SP Page Builder (Free and Pro) extension for Joomla 8.6 High 2026-09-14
CVE-2026-82232 Apache Syncope: SQL injection via sort parameter in Task search — Apache Syncope - - 2026-09-14
CVE-2026-86460 Apache Syncope: Cypher Injection via FIQL Search on Neo4j Persistence — Apache Syncope - - 2026-09-14

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