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

Goal: 1000 CNY · Raised: 1000 CNY

100.0%

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

9025 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-2025-42889 SQL Injection vulnerability in SAP Starter Solution (PL SAFT) — SAP Starter Solution (PL SAFT) 5.4 Medium2025-11-11
CVE-2025-64519 TorrentPier is Vulnerable to Authenticated SQL Injection through Moderator Control Panel's topic_id parameter — torrentpier 8.8 High2025-11-10
CVE-2025-12939 SourceCodester Interview Management System addCandidate.php sql injection — Interview Management System 6.3 Medium2025-11-10
CVE-2025-12938 projectworlds Online Admission System process_login.php sql injection — Online Admission System 7.3 High2025-11-10
CVE-2025-12409 SQL Injection in Looker Studio — Looker Studio 8.1 -2025-11-10
CVE-2025-12397 SQL Injection in Looker Studio — Looker Studio 8.8 -2025-11-10
CVE-2025-12933 SourceCodester Baby Care System updatewelcome.php sql injection — Baby Care System 6.3 Medium2025-11-10
CVE-2025-12932 SourceCodester Baby Care System admin.php sql injection — Baby Care System 4.7 Medium2025-11-10
CVE-2025-12931 SourceCodester Food Ordering System edit-orders.php sql injection — Food Ordering System 6.3 Medium2025-11-10
CVE-2025-12930 SourceCodester Food Ordering System view-ticket.php sql injection — Food Ordering System 6.3 Medium2025-11-10
CVE-2025-12929 SourceCodester Survey Application System LoginRegistration.php update_user sql injection — Survey Application System 7.3 High2025-11-10
CVE-2025-12928 code-projects Online Job Search Engine login.php sql injection — Online Job Search Engine 7.3 High2025-11-10
CVE-2025-12927 DedeBIZ archives_add.php sql injection — DedeBIZ 4.7 Medium2025-11-10
CVE-2025-12865 e-Excellence|U-Office Force - SQL Injection — U-Office Force 8.8 High2025-11-10
CVE-2025-12864 e-Excellence|U-Office Force - SQL Injection — U-Office Force 8.8 High2025-11-10
CVE-2025-12926 SourceCodester Farm Management System review.php sql injection — Farm Management System 6.3 Medium2025-11-10
CVE-2025-12914 aaPanel BaoTa Backend database sql injection — BaoTa 4.7 Medium2025-11-08
CVE-2025-12913 code-projects Responsive Hotel Site roomdel.php sql injection — Responsive Hotel Site 4.7 Medium2025-11-08
CVE-2025-11980 Quick Featured Images <= 13.7.3 - Authenticated (Editor+) SQL Injection via delete_orphaned — Quick Featured Images 4.9 Medium2025-11-08
CVE-2025-11972 Tag, Category, and Taxonomy Manager – AI Autotagger with OpenAI <= 3.40.0 - Authenticated (Editor+) SQL Injection — Tag, Category, and Taxonomy Manager – AI Autotagger with OpenAI 4.9 Medium2025-11-08
CVE-2025-11452 Asgaros Forum <= 3.1.0 - Unauthenticated SQL Injection — Asgaros Forum 7.5 High2025-11-08
CVE-2025-64493 SuiteCRM is Vulnerable to Authenticated Blind SQL Injection via GraphQL — SuiteCRM-Core 6.5 Medium2025-11-08
CVE-2025-64492 SuiteCRM is Vulnerable to Authenticated Time Based Blind SQL Injection — SuiteCRM-Core 8.8 High2025-11-08
CVE-2025-64488 SuiteCRM: Authenticated SQL Injection Possible in Reschedule Call Module — SuiteCRM 8.8 -2025-11-07
CVE-2025-12873 Campcodes School File Management update_user.php sql injection — School File Management 4.7 Medium2025-11-07
CVE-2025-12861 DedeBIZ spec_add.php sql injection — DedeBIZ 4.7 Medium2025-11-07
CVE-2025-52425 QuMagie — QuMagie 9.8 -2025-11-07
CVE-2025-12860 DedeBIZ freelist_main.php sql injection — DedeBIZ 4.7 Medium2025-11-07
CVE-2025-12859 DedeBIZ templets_one_edit.php sql injection — DedeBIZ 4.7 Medium2025-11-07
CVE-2025-12857 code-projects Responsive Hotel Site roombook.php sql injection — Responsive Hotel Site 4.7 Medium2025-11-07

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