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-2026-2058 mathurvishal CloudClassroom-PHP-Project Post Query Details postquerypublic.php sql injection — CloudClassroom-PHP-Project 7.3 High 2026-02-06
CVE-2026-2057 SourceCodester Medical Center Portal Management System login.php sql injection — Medical Center Portal Management System 7.3 High 2026-02-06
CVE-2026-2018 itsourcecode School Management System controller.php sql injection — School Management System 7.3 High 2026-02-06
CVE-2026-2014 itsourcecode Student Management System index.php sql injection — Student Management System 7.3 High 2026-02-06
CVE-2026-2013 itsourcecode Student Management System index.php sql injection — Student Management System 7.3 High 2026-02-06
CVE-2026-2012 itsourcecode Student Management System index.php sql injection — Student Management System 7.3 High 2026-02-06
CVE-2026-2011 itsourcecode Student Management System controller.php sql injection — Student Management System 7.3 High 2026-02-06
CVE-2026-21643 Fortinet FortiClientEMS SQL注入漏洞 — FortiClientEMS 9.1 Critical 2026-02-06
CVE-2025-15325 Tanium addressed an improper input validation vulnerability in Discover. — Discover 6.3 Medium 2026-02-05
CVE-2020-37151 phpMyChat Plus 1.98 'deluser.php' SQL Injection — phpMyChat Plus 8.2 High 2026-02-05
CVE-2025-13379 A SQL Injection vulnerability has been addressed in IBM Aspera Console — Aspera Console 8.6 High 2026-02-05
CVE-2026-1517 iomad Company Admin Block sql injection — iomad 4.7 Medium 2026-02-05
CVE-2025-13192 Popup builder with Gamification <= 2.2.0 - Unauthenticated SQL Injection via Multiple REST API Endpoints — Popup builder with Gamification, Multi-Step Popups, Page-Level Targeting, and WooCommerce Triggers 8.2 High 2026-02-04
CVE-2026-25513 FacturaScripts has SQL Injection vulnerability in API ORDER BY Clause — facturascripts 8.8AI High AI 2026-02-04
CVE-2025-69215 OpenSTAManager has an SQL Injection in the Stampe Module — openstamanager 8.8AI High AI 2026-02-04
CVE-2025-69213 OpenSTAManager has a SQL Injection in ajax_complete.php (get_sedi endpoint) — openstamanager 8.8AI High AI 2026-02-04
CVE-2026-22044 GLPI is Vulnerable to Authenticated SQL Injection — glpi 6.5 Medium 2026-02-04
CVE-2025-5329 SQLi in Martcode Software's Delta Course Automation — Delta Course Automation 9.8 Critical 2026-02-04
CVE-2026-0816 All push notification for WP <= 1.5.3 - Authenticated (Administrator+) SQL Injection via 'delete_id' Parameter — All push notification for WP 4.9 Medium 2026-02-04
CVE-2026-1370 SIBS - WooCommerce <= 2.2.0 - Authenticated (Admin+) SQL Injection via 'referencedId' Parameter — SIBS woocommerce payment gateway 4.9 Medium 2026-02-04
CVE-2025-15268 Infility Global <= 2.14.46 - Unauthenticated SQL Injection via Predictable API Key and IP Whitelist Bypass — Infility Global 7.5 High 2026-02-04
CVE-2020-37089 School ERP Pro 1.0 - 'es_messagesid' SQL Injection — School ERP Pro 8.2 High 2026-02-03
CVE-2020-37083 addressbook 9.0.0.1 - 'id' SQL Injection — PHP Address Book 8.2 High 2026-02-03
CVE-2020-37081 Fishing Reservation System 7.5 - 'uid' SQL Injection — Fishing Reservation System 7.1 High 2026-02-03
CVE-2020-37076 Victor CMS 1.0 - 'post' SQL Injection — CMSsite 8.2 High 2026-02-03
CVE-2019-25260 OXID eShop 6.3.4 - 'sorting' SQL Injection — OXID eShop 8.2 High 2026-02-03
CVE-2026-25241 PEAR is Vulnerable to SQL Injection in /get/<package>/<version> Endpoint — pearweb 9.8AI Critical AI 2026-02-03
CVE-2026-25240 PEAR is Vulnerable to SQL Injection in user::maintains() Role IN() Filter — pearweb 8.8AI High AI 2026-02-03
CVE-2026-25239 PEAR is Vulnerable to SQL Injection in apidoc_queue Insert via Unescaped Filename — pearweb 9.1AI Critical AI 2026-02-03
CVE-2026-25238 PEAR is Vulnerable to SQL Injection in Bug Subscription Deletion via Weak Email Validation — pearweb 9.8AI Critical AI 2026-02-03

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