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

Goal: 1000 CNY · Raised: 1000 CNY

100.0%

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

8957 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, AvailabilityExecute 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.
ConfidentialityRead Application Data
Since SQL databases generally hold sensitive data, loss of confidentiality is a frequent problem with SQL injection vulnerabilities.
AuthenticationGain 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 ControlBypass 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.
IntegrityModify 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 DesignUse 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 DesignIf 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, OperationRun 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 DesignFor 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.
ImplementationWhile 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 IDTitleCVSSSeverityPublished
CVE-2026-3150 itsourcecode College Management System display-teacher.php sql injection — College Management System 6.3 Medium2026-02-25
CVE-2026-3149 itsourcecode College Management System asign-single-student-subjects.php sql injection — College Management System 6.3 Medium2026-02-25
CVE-2026-3148 SourceCodester Simple and Nice Shopping Cart Script signup.php sql injection — Simple and Nice Shopping Cart Script 7.3 High2026-02-25
CVE-2026-27743 SPIP referer_spam <= 1.2.1 Unauthenticated SQL Injection — referer_spam 9.8 Critical2026-02-25
CVE-2026-27747 SPIP interface_traduction_objets < 2.2.2 Authenticated SQL Injection — interface_traduction_objets 8.8 High2026-02-25
CVE-2026-3135 itsourcecode News Portal Project add-category.php sql injection — News Portal Project 7.3 High2026-02-25
CVE-2026-3134 itsourcecode News Portal Project edit-category.php sql injection — News Portal Project 7.3 High2026-02-24
CVE-2026-3133 itsourcecode Document Management System Login loging.php sql injection — Document Management System 7.3 High2026-02-24
CVE-2026-21410 InSAT MasterSCADA BUK-TS SQL Injection — MasterSCADA BUK-TS 9.8 Critical2026-02-24
CVE-2026-3105 SQL Injection in Contact Activity API Sorting — Mautic 7.6 High2026-02-24
CVE-2026-23969 Apache Superset: Exposure of Sensitive Information via Incomplete ClickHouse Function Filtering — Apache Superset 9.8 -2026-02-24
CVE-2026-23980 Apache Superset: Improper Neutralization of Special Elements used in a SQL Command — Apache Superset 8.8 -2026-02-24
CVE-2025-11165 DotCMS 安全漏洞 — dotCMS 9.9AICriticalAI2026-02-24
CVE-2026-3069 itsourcecode Document Management System edtlbls.php sql injection — Document Management System 7.3 High2026-02-24
CVE-2026-3068 itsourcecode Document Management System deluser.php sql injection — Document Management System 7.3 High2026-02-24
CVE-2026-27461 Pimcore vulnerable to SQL injection via unsanitized filter value in Dependency Dao RLIKE clause — pimcore 4.9 -2026-02-24
CVE-2026-26198 ormar is vulnerable to SQL Injection through aggregate functions min() and max() — ormar 9.8 Critical2026-02-24
CVE-2026-3057 a54552239 pearProjectApi Backend Task.php dateTotalForProject sql injection — pearProjectApi 6.3 Medium2026-02-24
CVE-2026-3046 itsourcecode E-Logbook with Health Monitoring System for COVID-19 check_profile_old.php sql injection — E-Logbook with Health Monitoring System for COVID-19 7.3 High2026-02-24
CVE-2026-3042 itsourcecode Event Management System index.php sql injection — Event Management System 7.3 High2026-02-23
CVE-2025-41002 SQL injection in Infoticketing — Infoticketing 9.8AICriticalAI2026-02-23
CVE-2026-1367 SQL Injection — ManageEngine ADSelfService Plus 8.3 High2026-02-23
CVE-2026-24494 SQL injection vulnerability in Order Up Online Ordering System — Online Ordering System 9.8 Critical2026-02-23
CVE-2026-2963 Jinher OA C6 OfficeSupplyTypeRight.aspx sql injection — OA C6 6.3 Medium2026-02-23
CVE-2019-25462 Web Ofisi Rent a Car v3 SQL Injection via klima Parameter — Rent a Car 8.2 High2026-02-22
CVE-2019-25461 Web Ofisi Platinum E-Ticaret v5 SQL Injection via ajax/productsFilterSearch — Ticaret 7.5 High2026-02-22
CVE-2019-25460 Web Ofisi Platinum E-Ticaret v5 SQL Injection via q Parameter — Ticaret 7.5 High2026-02-22
CVE-2019-25459 Web Ofisi Emlak V2 SQL Injection via emlak-ara.html — Emlak 9.8 Critical2026-02-22
CVE-2019-25458 Web Ofisi Firma Rehberi v1 SQL Injection via firmalar.html — Firma Rehberi 9.8 Critical2026-02-22
CVE-2019-25457 Web Ofisi Firma v13 SQL Injection via oz Parameter — Firma 7.5 High2026-02-22

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