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

Goal: 1000 CNY · Raised: 1336 CNY

100%

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

10280 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, Availability Execute 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.
Confidentiality Read Application Data
Since SQL databases generally hold sensitive data, loss of confidentiality is a frequent problem with SQL injection vulnerabilities.
Authentication Gain 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 Control Bypass 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.
Integrity Modify 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 Design Use 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 Design If 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, Operation Run 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 Design For 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.
Implementation While 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 ID Title CVSS Severity Published
CVE-2026-3747 itsourcecode University Management System add_result.php sql injection — University Management System 7.3 High 2026-03-08
CVE-2026-3746 SourceCodester Simple Responsive Tourism Website Login Login.php sql injection — Simple Responsive Tourism Website 7.3 High 2026-03-08
CVE-2026-3745 code-projects Student Web Portal profile.php sql injection — Student Web Portal 6.3 Medium 2026-03-08
CVE-2026-3744 code-projects Student Web Portal signup.php valreg_passwdation sql injection — Student Web Portal 7.3 High 2026-03-08
CVE-2026-3740 itsourcecode University Management System admin_search_student.php sql injection — University Management System 7.3 High 2026-03-08
CVE-2026-3736 code-projects Simple Flight Ticket Booking System SearchResultRoundtrip.php sql injection — Simple Flight Ticket Booking System 7.3 High 2026-03-08
CVE-2026-3735 code-projects Simple Flight Ticket Booking System SearchResultOneway.php sql injection — Simple Flight Ticket Booking System 7.3 High 2026-03-08
CVE-2026-3730 itsourcecode Free Hotel Reservation System index.php sql injection — Free Hotel Reservation System 7.3 High 2026-03-08
CVE-2026-3723 code-projects Simple Flight Ticket Booking System Admindelete.php sql injection — Simple Flight Ticket Booking System 7.3 High 2026-03-08
CVE-2026-3711 code-projects Simple Flight Ticket Booking System Adminupdate.php sql injection — Simple Flight Ticket Booking System 4.7 Medium 2026-03-08
CVE-2026-3710 code-projects Simple Flight Ticket Booking System Adminadd.php sql injection — Simple Flight Ticket Booking System 4.7 Medium 2026-03-08
CVE-2026-3709 code-projects Simple Flight Ticket Booking System register.php sql injection — Simple Flight Ticket Booking System 7.3 High 2026-03-08
CVE-2026-3708 code-projects Simple Flight Ticket Booking System login.php sql injection — Simple Flight Ticket Booking System 7.3 High 2026-03-08
CVE-2026-3705 code-projects Simple Flight Ticket Booking System Adminsearch.php sql injection — Simple Flight Ticket Booking System 7.3 High 2026-03-08
CVE-2026-3672 JeecgBoot getDictItems isExistSqlInjectKeyword sql injection — JeecgBoot 6.3 Medium 2026-03-07
CVE-2026-30860 WeKnora: Remote Code Execution via SQL Injection Bypass in AI Database Query Tool — WeKnora 10.0 Critical 2026-03-07
CVE-2026-2429 Community Events <= 1.5.8 - Authenticated (Administrator+) SQL Injection via 'ce_venue_name' CSV Field — Community Events 4.9 Medium 2026-03-07
CVE-2025-14353 ZIP Code Based Content Protection <= 1.0.2 - Unauthenticated SQL Injection via 'zipcode' Parameter — ZIP Code Based Content Protection 7.5 High 2026-03-07
CVE-2018-25199 OOP CMS BLOG 1.0 SQL Injection via search parameter — OOP CMS BLOG 8.2 High 2026-03-06
CVE-2018-25197 PlayJoom 0.10.1 SQL Injection via catid Parameter — PlayJoom 8.2 High 2026-03-06
CVE-2018-25196 ServerZilla 1.0 SQL Injection via email Parameter — ServerZilla 8.2 High 2026-03-06
CVE-2018-25191 Facturation System 1.0 SQL Injection via editar_producto.php — Facturation System 7.1 High 2026-03-06
CVE-2018-25192 GPS Tracking System 2.12 SQL Injection via username Parameter — GPS Tracking System 8.2 High 2026-03-06
CVE-2018-25189 Data Center Audit 2.6.2 SQL Injection via username Parameter — Data Center Audit 8.2 High 2026-03-06
CVE-2018-25187 Tina4 Stack 1.0.3 SQL Injection and Database File Download — Tina4 Stack 8.2 High 2026-03-06
CVE-2018-25188 Webiness Inventory 2.3 SQL Injection via WsModelGrid.php — Webiness Inventory 8.2 High 2026-03-06
CVE-2018-25182 Silurus Classifieds Script 2.0 SQL Injection via wcategory.php — Silurus Classifieds Script 8.2 High 2026-03-06
CVE-2018-25180 Maitra 1.7.2 SQL Injection and Database File Download — Maitra 7.1 High 2026-03-06
CVE-2018-25179 Gumbo CMS 0.99 SQL Injection via settings endpoint — Gumbo CMS 8.2 High 2026-03-06
CVE-2018-25175 Alienor Web Libre 2.0 SQL Injection via index.php — Alienor Web Libre 8.2 High 2026-03-06

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