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

Goal: 1000 CNY · Raised: 1000 CNY

100.0%

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

9028 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-32786 GLPI Inventory Plugin is Vulnerable to Unauthenticated SQL Injection — glpi-inventory-plugin 7.5 High2025-11-04
CVE-2025-12463 Unauthenticated SQL Injection in Guetebruck G-Cam Series Cameras — G-Cam 9.8 Critical2025-11-03
CVE-2025-12503 Digiwin|EasyFlow .NET and EasyFlow AiNet — EasyFlow .NET 6.5 Medium2025-11-03
CVE-2025-12617 itsourcecode Billing System login_crud.php sql injection — Billing System 7.3 High2025-11-03
CVE-2025-12614 SourceCodester Best House Rental Management System admin_class.php delete_payment sql injection — Best House Rental Management System 4.7 Medium2025-11-03
CVE-2025-12612 Campcodes School Fees Payment Management System ajax.php sql injection — School Fees Payment Management System 6.3 Medium2025-11-03
CVE-2025-12610 CodeAstro Gym Management System view-progress-report.php sql injection — Gym Management System 4.7 Medium2025-11-03
CVE-2025-12609 CodeAstro Gym Management System update-progress.php sql injection — Gym Management System 4.7 Medium2025-11-03
CVE-2025-12608 itsourcecode Online Loan Management System manage_user.php sql injection — Online Loan Management System 7.3 High2025-11-03
CVE-2025-12607 itsourcecode Online Loan Management System manage_payment.php sql injection — Online Loan Management System 7.3 High2025-11-03
CVE-2025-12606 itsourcecode Online Loan Management System manage_borrower.php sql injection — Online Loan Management System 7.3 High2025-11-02
CVE-2025-12605 itsourcecode Online Loan Management System manage_loan.php sql injection — Online Loan Management System 7.3 High2025-11-02
CVE-2025-12604 itsourcecode Online Loan Management System load_fields.php sql injection — Online Loan Management System 7.3 High2025-11-02
CVE-2025-12598 SourceCodester Best House Rental Management System admin_class.php save_tenant sql injection — Best House Rental Management System 4.7 Medium2025-11-02
CVE-2025-12597 SourceCodester Best House Rental Management System admin_class.php save_category sql injection — Best House Rental Management System 4.7 Medium2025-11-02
CVE-2025-12594 code-projects Simple Online Hotel Reservation System add_account.php sql injection — Simple Online Hotel Reservation System 4.7 Medium2025-11-02
CVE-2025-11740 wpForo Forum <= 2.4.9 - Authenticated (Susbscriber+) SQL Injection — wpForo Forum 6.5 Medium2025-11-01
CVE-2025-64366 WordPress MasterStudy LMS plugin <= 3.6.27 - SQL Injection vulnerability — MasterStudy LMS 7.6 High2025-10-31
CVE-2025-6520 SQLi in Abis Technology's BAPSIS — BAPSIS 9.8 Critical2025-10-31
CVE-2020-36869 Nagios XI < 5.7.5 SQL injection via SNMP Trap Interface Edit Page — XI 7.2AIHighAI2025-10-30
CVE-2016-15050 Nagios XI < 5.2.4 SQL Injection in Notification Search — XI 8.1AIHighAI2025-10-30
CVE-2020-36859 Nagios XI < 5.7.4 Core Config Manager (CCM) SQL Injection via Object Edit Pages — XI 8.8AIHighAI2025-10-30
CVE-2021-47693 Nagios XI < 5.8.5 Core Config Manager (CCM) SQL Injection via Improper Escaping in Search Text — XI 8.8AIHighAI2025-10-30
CVE-2020-36857 Nagios XI < 5.6.14 Authenticated SQL Injection via SNMP Trap Interface Page — XI 7.2AIHighAI2025-10-30
CVE-2012-10063 Nagios XI < 2012R1.3 Authenticated SQL Injection in Legacy CCM — XI 8.1AIHighAI2025-10-30
CVE-2025-64104 LangGraph SQLite Checkpoint Filter Key SQL Injection POC for SqliteStore — langgraph 7.3 High2025-10-29
CVE-2015-10147 Easy Testimonial Slider and Form <= 1.0.2 - Authenticated (Admin+) SQL injection — Easy Testimonial Slider and Form 4.9 Medium2025-10-29
CVE-2015-10146 Thumbnail Slider With Lightbox <= 1.0.4 - Authenticated (Admin+) SQL Injection — Thumbnail Slider With Lightbox 4.9 Medium2025-10-29
CVE-2025-4665 WordPress plugin Contact Form CFDB7 安全漏洞 — CFDB7 9.6 Critical2025-10-28
CVE-2025-62367 Taiga Blind SQL Injection Time Based — taiga-back 4.8 Medium2025-10-28

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