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

Goal: 1000 CNY · Raised: 1336 CNY

100%

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

10268 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-10110 code-projects Student Details Management System index.php sql injection — Student Details Management System 7.3 High 2026-05-30
CVE-2026-10105 agno 2.6.5 SQL Injection via ClickHouse delete_by_metadata() — agno 8.3 High 2026-05-29
CVE-2018-25404 The Open ISES Project 3.30A SQL Injection via add_facnote.php — Open ISES Project 8.2 High 2026-05-29
CVE-2018-25403 The Open ISES Project 3.30A SQL Injection via city_graph.php — Open ISES Project 8.2 High 2026-05-29
CVE-2018-25402 The Open ISES Project 3.30A SQL Injection via inc_types_graph.php — Open ISES Project 8.2 High 2026-05-29
CVE-2018-25401 The Open ISES Project 3.30A SQL Injection via sever_graph.php — Open ISES Project 8.2 High 2026-05-29
CVE-2018-25399 The Open ISES Project 3.30A SQL Injection via nearby.php — Open ISES Project 8.2 High 2026-05-29
CVE-2018-25400 The Open ISES Project 3.30A SQL Injection via form_post.php — Open ISES Project 8.2 High 2026-05-29
CVE-2018-25398 The Open ISES Project 3.30A SQL Injection via main.php — Open ISES Project 8.2 High 2026-05-29
CVE-2018-25395 Kados R10 GreenBee SQL Injection via update_feature.php — Kados R10 GreenBee 8.2 High 2026-05-29
CVE-2018-25394 Kados R10 GreenBee SQL Injection via update_release.php — Kados R10 GreenBee 8.2 High 2026-05-29
CVE-2018-25392 MaxOn ERP Software 8.x-9.x SQL Injection via nomor Parameter — MaxOn ERP 7.1 High 2026-05-29
CVE-2018-25390 HaPe PKH 1.1 SQL Injection via desa Parameter — HaPe PKH 8.2 High 2026-05-29
CVE-2018-25389 HaPe PKH 1.1 SQL Injection via nama_kelompok Parameter — HaPe PKH 8.2 High 2026-05-29
CVE-2018-25386 HaPe PKH 1.1 SQL Injection via id Parameter in admin/media.php — HaPe PKH 8.2 High 2026-05-29
CVE-2018-25385 E-Registrasi Pencak Silat 18.10 SQL Injection via id_partai — Registrasi Pencak Silat 8.2 High 2026-05-29
CVE-2018-25382 Zechat 1.5 SQL Injection via uname Parameter — Zechat 8.2 High 2026-05-29
CVE-2026-44238 FreePBX: Authenticated SQL Injection via ORDER BY in CDR Reports — security-reporting - - 2026-05-29
CVE-2026-10039 Frontend Admin by DynamiApps <= 3.28.28 - Authenticated (Administrator+) SQL Injection via 'order' Parameter — Frontend Admin by DynamiApps 4.9 Medium 2026-05-29
CVE-2026-4776 Mautic 安全漏洞 7.1 High 2026-05-29
CVE-2026-45288 Marten has an SQL injection vulnerability in its full-text search regConfig parameter — marten 9.8 Critical 2026-05-28
CVE-2026-7048 Photo Gallery by 10Web <= 1.8.40 - Authenticated (Contributor+) SQL Injection via 'order_by' Shortcode Attribute — Photo Gallery by 10Web – Mobile-Friendly Image Gallery 6.5 Medium 2026-05-28
CVE-2026-7797 Appointment Booking Calendar <= 1.6.11.8 - Unauthenticated SQL Injection via 'append_where_sql' Parameter — Appointment Booking Calendar — Simply Schedule Appointments Booking Plugin 7.5 High 2026-05-28
CVE-2026-44886 Pi.Alert: Web Interface Vulnerable to Unauthenticated Blind SQL Injection — Pi.Alert - - 2026-05-27
CVE-2026-44521 elFinder: SQL Injection MySQL Volume Driver (elFinderVolumeMySQL) — elFinder 8.8 High 2026-05-27
CVE-2026-49046 WordPress Duplicate Page and Post plugin <= 2.9.5 - SQL Injection vulnerability — Duplicate Page and Post 8.5 High 2026-05-27
CVE-2026-9617 PostgreSQL Anonymizer: malicious column name allows SQL injection via anon.k_anonymity() function — PostgreSQL Anonymizer 6.8 Medium 2026-05-27
CVE-2026-42761 WordPress Active Products Tables for WooCommerce plugin <= 1.0.9 - SQL Injection vulnerability — Active Products Tables for WooCommerce 9.3 Critical 2026-05-27
CVE-2026-42755 WordPress TableOn plugin <= 1.0.5.1 - SQL Injection vulnerability — TableOn 9.3 Critical 2026-05-27
CVE-2026-42747 WordPress Easy Form Builder plugin <= 4.0.6 - SQL Injection vulnerability — Easy Form Builder 9.3 Critical 2026-05-27

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