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

Goal: 1000 CNY · Raised: 1336 CNY

100%

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

10247 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-18854 Shandong Hoteam PDM Product Data Management System DataService GetStoredClassByFilter sql injection — PDM Product Data Management System 7.3 High 2026-08-05
CVE-2026-69704 Atals-Livre SQL Injection via Unsanitized GET Parameter in supp() — Atals-Livre 6.5 Medium 2026-08-04
CVE-2026-64631 Veeam ONE SQL注入漏洞 — ONE 8.6 High 2026-08-04
CVE-2026-18766 chetans9 core-php-admin-panel customers.php sql injection — core-php-admin-panel 6.3 Medium 2026-08-04
CVE-2026-70373 Koha - SQL Injection in reports/issues_stats.pl — Koha 8.8 High 2026-08-04
CVE-2026-70372 Koha - SQL Injection in reports/bor_issues_top.pl — Koha 8.8 High 2026-08-04
CVE-2026-70371 Koha - SQL Injection in reports/issues_avg_stats.pl — Koha 8.8 High 2026-08-04
CVE-2026-70370 Koha - SQL Injection in reports/catalogue_stats.pl — Koha 8.8 High 2026-08-04
CVE-2026-70369 Koha - SQL Injection in reports/acquisitions_stats.pl — Koha 8.8 High 2026-08-04
CVE-2026-18719 cemtan sar2html Search sar2html.py sql injection — sar2html 6.3 Medium 2026-08-04
CVE-2026-48330 Adobe Campaign Classic (ACC) | Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') (CWE-89) — Adobe Campaign Classic 10.0 Critical 2026-08-03
CVE-2026-48326 Adobe Campaign Classic (ACC) | Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') (CWE-89) — Adobe Campaign Classic 9.9 Critical 2026-08-03
CVE-2026-18737 Shlink Blind SQL Injection via tags/stats orderBy Parameter — Shlink 6.5 Medium 2026-08-03
CVE-2026-69240 Sequelize: SQL Injection (Oracle DB) — sequelize 9.8 Critical 2026-08-03
CVE-2026-41453 Krayin CRM < 2.2.4 Blind SQL Injection via LeadDataGrid.php rotten_lead Parameter — laravel-crm 8.8 High 2026-08-03
CVE-2026-69085 SiYuan before v3.7.3 SQL Injection via searchDocs — siyuan 10.0 Critical 2026-08-03
CVE-2026-69084 SiYuan before v3.7.3 SQL Injection via searchEmbedBlock — siyuan 10.0 Critical 2026-08-03
CVE-2026-69083 SiYuan before v3.7.3 SQL Injection via fullTextSearchAssetContent — siyuan 10.0 Critical 2026-08-03
CVE-2026-18592 osCommerce Email Template Configuration EmailController.php EmailController sql injection — osCommerce 4.7 Medium 2026-08-03
CVE-2026-65321 PyAthena SQL Injection via DefaultParameterFormatter DELETE/CTAS — PyAthena 9.8 Critical 2026-08-02
CVE-2026-6453 CubeWP Framework <= 1.1.30 - Authenticated (Subscriber+) SQL Injection via 'relation_id' Parameter — CubeWP Framework 6.5 Medium 2026-08-01
CVE-2026-17555 WPvivid <= 0.9.131 - Authenticated (Administrator+) SQL Injection via 'export_data' Parameter — WPvivid — Backup, Migration & Staging 4.9 Medium 2026-08-01
CVE-2026-15951 Icegram Mailer <= 1.0.12 - Authenticated (Administrator+) SQL Injection via 'fields' Parameter — Icegram Mailer – Reliable Email Deliverability, No-code SMTP Replacement & Email logs 4.9 Medium 2026-08-01
CVE-2026-15018 Database Collation Fix <= 1.2.10 - Unauthenticated SQL Injection via 'force-collation-algorithm' Parameter — Database Collation Fix 5.3 Medium 2026-08-01
CVE-2026-16614 GSheetConnector <= 5.2.1 - Authenticated (Administrator+) SQL Injection via 's' Parameter — GSheetConnector – CF7 Google Sheets Connector 4.9 Medium 2026-08-01
CVE-2026-16087 Icegram Engage <= 3.1.42 - Authenticated (Contributor+) Second-Order SQL Injection via 'messages[][id]' Parameter — Icegram Engage – Popups, Optins, CTAs & Lead Generation 6.5 Medium 2026-08-01
CVE-2026-15403 Pinpoint Booking System <= 2.9.9.6.9 - Authenticated (Administrator+) SQL Injection via 'field' Parameter — Pinpoint Booking System – Version 2 4.9 Medium 2026-08-01
CVE-2026-45376 Decidim: Admin user search allows SQL injection through similarity-based sorting — decidim 5.5 Medium 2026-07-31
CVE-2026-58048 WebPros cPanel SQL注入漏洞 — cPanel 9.4 Critical 2026-07-31
CVE-2026-17351 pgAdmin 4: AI Assistant read-only transaction bypass via sqlparse/PostgreSQL lexer disagreement (incomplete fix for CVE-2026-12045) — pgAdmin 4 9.0 Critical 2026-07-31

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