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

Goal: 1000 CNY · Raised: 1336 CNY

100%

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

10239 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-19354 lock-upme OPMS IN Clause message.go sql injection — OPMS 6.3 Medium 2026-08-09
CVE-2026-19351 dresende node-sql-query Request Parameter Select.js SelectQuery.build sql injection — node-sql-query 7.3 High 2026-08-09
CVE-2026-19347 itsourcecode Hospital Management System viewdoctor.php sql injection — Hospital Management System 6.3 Medium 2026-08-09
CVE-2026-19344 code-projects Task Management System comment_count_user.php sql injection — Task Management System 7.3 High 2026-08-09
CVE-2026-19343 code-projects Task Management System AdminLogin.php sql injection — Task Management System 7.3 High 2026-08-09
CVE-2026-19231 SourceCodester Simple Doctors Appointment System ajax.php delete_appointment sql injection — Simple Doctors Appointment System 7.3 High 2026-08-07
CVE-2025-58375 Frappe has potential SQL Injection due to missing validation — frappe 8.1 High 2026-08-07
CVE-2026-19211 SourceCodester Photo Share Website ajax.php signup sql injection — Photo Share Website 7.3 High 2026-08-07
CVE-2026-66838 SQL injection via the :comment option in Postgrex.stream/4 — postgrex 5.9 Medium 2026-08-07
CVE-2026-19196 SourceCodester Photo Share Website ajax.php login sql injection — Photo Share Website 7.3 High 2026-08-07
CVE-2026-19071 itsourcecode Hospital Management System viewappointment.php sql injection — Hospital Management System 6.3 Medium 2026-08-06
CVE-2026-19070 itsourcecode Hospital Management System viewadmin.php sql injection — Hospital Management System 6.3 Medium 2026-08-06
CVE-2026-19069 itsourcecode Hospital Management System treatmentrecord.php sql injection — Hospital Management System 6.3 Medium 2026-08-06
CVE-2026-19068 itsourcecode Hospital Management System treatmentdetail.php sql injection — Hospital Management System 6.3 Medium 2026-08-06
CVE-2026-19067 itsourcecode Hospital Management System treatment.php sql injection — Hospital Management System 6.3 Medium 2026-08-06
CVE-2026-19062 chiuwingyan house selectall.action sql injection — house 7.3 High 2026-08-06
CVE-2026-34191 Apache Portable Runtime Utility: SQL Injection in apr_dbd_oracle — Apache Portable Runtime Utility - - 2026-08-06
CVE-2026-66447 WordPress WordPress File Upload plugin <= 5.1.7 - SQL Injection vulnerability — WordPress File Upload 9.3 Critical 2026-08-06
CVE-2026-65569 WordPress WP Job Portal plugin <= 2.5.6 - SQL Injection vulnerability — WP Job Portal 8.5 High 2026-08-06
CVE-2026-65547 WordPress Creative Mail plugin <= 1.6.9 - SQL Injection vulnerability — Creative Mail 8.5 High 2026-08-06
CVE-2026-65546 WordPress Qode Tours plugin <= 3.1.3.1 - SQL Injection vulnerability — Qode Tours 9.3 Critical 2026-08-06
CVE-2026-65520 WordPress WP OAuth Server plugin <= 6.2.0 - SQL Injection vulnerability — WP OAuth Server 9.3 Critical 2026-08-06
CVE-2026-65508 WordPress Simply Schedule Appointments plugin <= 1.6.12.10 - SQL Injection vulnerability — Simply Schedule Appointments 9.3 Critical 2026-08-06
CVE-2026-5134 SQLi in Loca Software's CMS — CMS 9.8 Critical 2026-08-06
CVE-2026-19021 SourceCodester Computer Repair Shop Management System Master.php delete_product sql injection — Computer Repair Shop Management System 7.3 High 2026-08-06
CVE-2026-19020 itsourcecode Hospital Management System servicetype.php sql injection — Hospital Management System 6.3 Medium 2026-08-06
CVE-2026-18970 Rongzhitong Visual Integrated Command and Dispatch Platform findAll sql injection — Visual Integrated Command and Dispatch Platform 7.3 High 2026-08-05
CVE-2026-18958 imranrisal-dev Student-Management-System Login loginCheckTest.php sql injection — Student-Management-System 7.3 High 2026-08-05
CVE-2026-10716 Directus <12.1.0 - Authenticated time-based SQL injection in PostgreSQL/PostGIS collection creation — Directus 7.5 High 2026-08-05
CVE-2026-71292 Subrion CMS Admin Grid SQL Injection via Unwhitelisted ORDER BY sort Parameter — subrion 7.2 High 2026-08-05

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