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-5551 itsourcecode Free Hotel Reservation System Parameter login.php sql injection — Free Hotel Reservation System 7.3 High2026-04-05
CVE-2026-5543 PHPGurukul User Registration & Login and User Management System yesterday-reg-users.php sql injection — User Registration & Login and User Management System 6.3 Medium2026-04-05
CVE-2026-5540 code-projects Simple Laundry System Parameter modifymember.php sql injection — Simple Laundry System 7.3 High2026-04-05
CVE-2026-5537 halex CourseSEL HTTP GET Parameter IndexController.class.php check_sel sql injection — CourseSEL 6.3 Medium2026-04-05
CVE-2026-5534 itsourcecode Online Enrollment System Parameter index.php sql injection — Online Enrollment System 7.3 High2026-04-05
CVE-2026-34934 PraisonAI: Second-Order SQL Injection in `get_all_user_threads` — PraisonAI 9.8 Critical2026-04-03
CVE-2026-34612 Kestra: Remote Code Execution via SQL Injection — kestra 10.0 Critical2026-04-03
CVE-2026-34788 Emlog: SQL Injection in tag_model::updateTagName() via unsanitized parameters — emlog 6.5 Medium2026-04-03
CVE-2026-27885 Piwigo: SQL Injection in Activity.getList — Piwigo 7.2 High2026-04-03
CVE-2026-27834 Piwigo: SQL Injection in pwg.users.getList API Method via filter Parameter — Piwigo 7.2 High2026-04-03
CVE-2026-27634 Piwigo: Pre-auth SQL injection via date filter parameters in ws_std_image_sql_filter — Piwigo 7.5AIHighAI2026-04-03
CVE-2026-25773 Focalboard Second-Order SQL Injection in category reorder endpoint allows data exfiltration (unsupported product, no fix) — Focalboard 8.1 High2026-04-03
CVE-2026-34825 NocoBase Has SQL Injection via template variable substitution in workflow SQL node — nocobase 8.8AIHighAI2026-04-02
CVE-2026-34717 OpenProject: SQL Injection in Cost Reporting =n Operator via parse_number_string — openproject 9.9 Critical2026-04-02
CVE-2026-5368 projectworlds Car Rental Project Parameter login.php sql injection — Car Rental Project 7.3 High2026-04-02
CVE-2026-35168 OpenSTAManager: SQL Injection via Aggiornamenti Module — openstamanager 8.8 High2026-04-02
CVE-2026-5334 itsourcecode Online Enrollment System Parameter index.php sql injection — Online Enrollment System 7.3 High2026-04-02
CVE-2026-28805 OpenSTAManager: Time-Based Blind SQL Injection via `options[stato]` Parameter — openstamanager 8.8 High2026-04-02
CVE-2026-5328 shsuishang modulithshop ProductItemDao ProductIndexServiceImpl.java listItem sql injection — modulithshop 6.3 Medium2026-04-02
CVE-2026-33616 MB connect line mbCONNECT24 vulnerable to an unauthenticated SQL injection in the mb24api Endpoint — mbCONNECT24 7.5 High2026-04-02
CVE-2026-33615 MB connect line mbCONNECT24 vulnerable to an unauthenticated SQL injection in the setinfo Endpoint — mbCONNECT24 9.1 Critical2026-04-02
CVE-2026-33614 MB connect line mbCONNECT24 vulnerable to an unauthenticated SQL injection in the getinfo endpoint — mbCONNECT24 7.5 High2026-04-02
CVE-2026-5322 AlejandroArciniegas mcp-data-vis MCP server.js request sql injection — mcp-data-vis 7.3 High2026-04-02
CVE-2026-34455 Hi.Events: SQL Injection via Unvalidated sort_by Query Parameter in Multiple Repository Classes — Hi.Events 9.8AICriticalAI2026-04-01
CVE-2026-34747 Payload has an SQL Injection via Query Handling — payload 8.5 High2026-04-01
CVE-2026-21630 Joomla! Core - [20260302] - SQL injection in com_content articles webservice endpoint — Joomla! CMS 9.8AICriticalAI2026-04-01
CVE-2026-5257 code-projects Simple Laundry System Parameter delstaffinfo.php sql injection — Simple Laundry System 7.3 High2026-04-01
CVE-2026-5256 code-projects Simple Laundry System Parameter modify.php sql injection — Simple Laundry System 7.3 High2026-04-01
CVE-2025-13855 IBM Storage Protect Server is affected by a vulnerability that could allow authenticated users to access administrative metadata through the JSON-RPC endpoint . — Storage Protect Server 7.6 High2026-04-01
CVE-2026-5238 itsourcecode Payroll Management System Parameter view_employee.php sql injection — Payroll Management System 7.3 High2026-03-31

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