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

Goal: 1000 CNY · Raised: 1336 CNY

100%

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

10262 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-4104 SQLi in Akmer Informatics' TeknoPass — TeknoPass 9.8 Critical 2026-06-04
CVE-2026-49771 WordPress Photo Gallery by 10Web plugin <= 1.8.41 - SQL Injection vulnerability — Photo Gallery by 10Web 7.6 High 2026-06-04
CVE-2026-8653 MasterStudy LMS Pro Plus <= 4.8.20 - Authenticated (Instructor+) SQL Injection via 'columns' Parameter — MasterStudy LMS Pro 6.5 Medium 2026-06-04
CVE-2025-15655 WordPress School Management plugin <= 93.2.0 - SQL Injection vulnerability — School Management 7.6 High 2026-06-03
CVE-2026-10704 SourceCodester Pizzafy E-Commerce System Administrative Control Panel admin_class_novo.php login sql injection — Pizzafy E-Commerce System 7.3 High 2026-06-03
CVE-2026-10620 code-projects Student Admission System index.php sql injection — Student Admission System 7.3 High 2026-06-02
CVE-2026-5074 ARMember Premium <= 7.3.1 - Authenticated (Subscriber+) SQL Injection via 'sSortDir_0' Parameter — ARMember Premium – Membership Plugin, Content Restriction, Member Levels, User Profile & User signup 6.5 Medium 2026-06-02
CVE-2026-5073 ARMember Premium <= 7.3.1 - Unauthenticated SQL Injection via 'order' Parameter — ARMember Premium – Membership Plugin, Content Restriction, Member Levels, User Profile & User signup 7.5 High 2026-06-02
CVE-2026-10608 DedeCMS carbuyaction.php RemoveXSS sql injection — DedeCMS 7.3 High 2026-06-02
CVE-2026-10607 DedeCMS flink.php dede_htmlspecialchars sql injection — DedeCMS 7.3 High 2026-06-02
CVE-2026-10606 DedeCMS Feedback feedback.php TrimMsg sql injection — DedeCMS 7.3 High 2026-06-02
CVE-2026-42684 WordPress WP Job Portal plugin <= 2.5.1 - SQL Injection vulnerability — WP Job Portal 9.3 Critical 2026-06-02
CVE-2026-10568 itsourcecode Fees Management System manage_payment.php sql injection — Fees Management System 6.3 Medium 2026-06-02
CVE-2026-10302 itsourcecode Fees Management System manage_fee.php sql injection — Fees Management System 6.3 Medium 2026-06-01
CVE-2026-25879 Langroid has Prompt to SQL Injection, Leading to RCE — langroid 9.8 Critical 2026-06-01
CVE-2026-10297 itsourcecode Fees Management System manage_course.php sql injection — Fees Management System 6.3 Medium 2026-06-01
CVE-2026-24782 Kiteworks Secure Data Forms has a SQL Injection vulnerability — Secure Data Forms 7.6 High 2026-06-01
CVE-2026-10296 itsourcecode Fees Management System ajax.php sql injection — Fees Management System 6.3 Medium 2026-06-01
CVE-2026-49491 Pixa Bank 2.0 SQL Injection via agence-ajax.php API — Pixa Bank 8.2 High 2026-06-01
CVE-2018-25434 WP AutoSuggest 0.24 SQL Injection via autosuggest.php — WP AutoSuggest 8.2 High 2026-06-01
CVE-2018-25433 Joomla JE Photo Gallery 1.1 SQL Injection via categoryid — JE Photo Gallery 8.2 High 2026-06-01
CVE-2018-25431 No-Cms 1.0 SQL Injection via order_by Parameter — No-CMS 7.1 High 2026-06-01
CVE-2018-25430 Paroiciel 11.20 SQL Injection via eGeqIdEquipe Parameter — Paroiciel 7.1 High 2026-06-01
CVE-2018-25429 Paroiciel 11.20 SQL Injection via zProIdPro Parameter — Paroiciel 7.1 High 2026-06-01
CVE-2018-25428 Paroiciel 11.20 SQL Injection via tRecIdListe Parameter — Paroiciel 8.2 High 2026-06-01
CVE-2026-10290 code-projects Hotel and Tourism Reservation System GET Parameter tour.php sql injection — Hotel and Tourism Reservation System 7.3 High 2026-06-01
CVE-2026-10286 CodeAstro Payroll System home_employee.php sql injection — Payroll System 6.3 Medium 2026-06-01
CVE-2026-45722 Nextcloud: Tables app allows limited SQLi in ORDER BY with malicious sort order argument for Table Views — security-advisories 7.1 High 2026-06-01
CVE-2026-45545 Nextcloud: SQL Injection in Column Type Parameter Allows Arbitrary SQL Execution — security-advisories 8.2 High 2026-06-01
CVE-2026-42672 WordPress WP Directory Kit plugin <= 1.5.1 - SQL Injection vulnerability — WP Directory Kit 9.3 Critical 2026-06-01

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