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-4612 itsourcecode Free Hotel Reservation System Parameter index.php sql injection — Free Hotel Reservation System 7.3 High2026-03-23
CVE-2026-4597 648540858 wvp-GB28181-pro Stream Proxy Query StreamProxyProvider.java selectAll sql injection — wvp-GB28181-pro 6.3 Medium2026-03-23
CVE-2026-33723 AVideo Vulnerable to SQL Injection in Subscribe Endpoint via Unsanitized user_id Parameter in subscribe.php — AVideo 7.1 High2026-03-23
CVE-2026-33651 AVideo has a Blind SQL Injection in Live Schedule Reminder via Unsanitized live_schedule_id in Scheduler_commands::getAllActiveOrToRepeat() — AVideo 8.1 High2026-03-23
CVE-2026-33485 AVideo has an Unauthenticated Blind SQL Injection in RTMP on_publish Callback via Stream Name Parameter — AVideo 7.5 High2026-03-23
CVE-2026-33352 AVideo has an Unauthenticated SQL Injection via `doNotShowCats` Parameter (Backslash Escape Bypass) — AVideo 9.8 Critical2026-03-23
CVE-2025-41008 SQL Injection in Sinturno — Sinturno 9.8 -2026-03-23
CVE-2025-41007 SQL Injection in Cuantis — Cuantis 9.8 -2026-03-23
CVE-2026-32969 Pre-Auth Blind SQLi in userinfo Endpoint — MB connect line mbCONNECT24 7.5 High2026-03-23
CVE-2026-4581 code-projects Simple Laundry System Parameters checklogin.php sql injection — Simple Laundry System 7.3 High2026-03-23
CVE-2026-4580 code-projects Simple Laundry System Parameters checkupdatestatus.php sql injection — Simple Laundry System 7.3 High2026-03-23
CVE-2026-4579 code-projects Simple Laundry System Parameters viewdetail.php sql injection — Simple Laundry System 7.3 High2026-03-23
CVE-2026-4574 SourceCodester Simple E-learning System User Profile Update sql injection — Simple E-learning System 6.3 Medium2026-03-23
CVE-2026-4573 SourceCodester Simple E-learning System HTTP GET Parameter delete_post.php sql injection — Simple E-learning System 6.3 Medium2026-03-23
CVE-2026-4572 SourceCodester Sales and Inventory System HTTP POST Request view_product.php sql injection — Sales and Inventory System 6.3 Medium2026-03-23
CVE-2026-4571 SourceCodester Sales and Inventory System HTTP POST Request view_payments.php sql injection — Sales and Inventory System 6.3 Medium2026-03-23
CVE-2026-4570 SourceCodester Sales and Inventory System HTTP POST Request view_customers.php sql injection — Sales and Inventory System 6.3 Medium2026-03-23
CVE-2026-4569 SourceCodester Sales and Inventory System HTTP POST Request view_category.php sql injection — Sales and Inventory System 6.3 Medium2026-03-23
CVE-2026-4568 SourceCodester Sales and Inventory System HTTP GET Request update_supplier.php sql injection — Sales and Inventory System 6.3 Medium2026-03-23
CVE-2026-2580 WP Maps – Store Locator,Google Maps,OpenStreetMap,Mapbox,Listing,Directory & Filters <= 4.9.1 - Unauthenticated SQL Injection via 'orderby' Parameter — WP Maps – Store Locator,Google Maps,OpenStreetMap,Mapbox,Listing,Directory & Filters 7.5 High2026-03-22
CVE-2026-4550 code-projects Simple Gym Management System func.php sql injection — Simple Gym Management System 4.7 Medium2026-03-22
CVE-2026-4540 projectworlds Online Notes Sharing System Parameters login.php sql injection — Online Notes Sharing System 7.3 High2026-03-22
CVE-2026-4533 code-projects Simple Food Ordering System all-tickets.php sql injection — Simple Food Ordering System 6.3 Medium2026-03-22
CVE-2026-4530 apconw Aix-DB terminology_retriever.py sql injection — Aix-DB 5.3 Medium2026-03-21
CVE-2019-25581 i-doit CMDB 1.12 SQL Injection via objGroupID Parameter — doit CMDB 8.2 High2026-03-21
CVE-2019-25578 phpTransformer 2016.9 SQL Injection via GeneratePDF.php — phpTransformer 8.2 High2026-03-21
CVE-2019-25576 Kepler Wallpaper Script 1.1 SQL Injection via category — Kepler Wallpaper Script 8.2 High2026-03-21
CVE-2019-25575 SimplePress CMS 1.0.7 SQL Injection via p and s Parameters — SimplePress CMS 8.2 High2026-03-21
CVE-2019-25573 Green CMS 2.x SQL Injection via cat Parameter — Green CMS 7.1 High2026-03-21
CVE-2026-4513 vanna-ai vanna base.py ask sql injection — vanna 6.3 Medium2026-03-21

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