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-2017-20265 Joomla! Component Flip Wall 8.0 SQL Injection — Flip Wall 7.1 High 2026-06-19
CVE-2017-20264 Joomla! Component Sponsor Wall 8.0 SQL Injection — Sponsor Wall 7.1 High 2026-06-19
CVE-2017-20263 Joomla! FocalPoint Pro Free 1.2.3 SQL Injection via location — FocalPoint Pro / Free 8.2 High 2026-06-19
CVE-2017-20262 Joomla! Component Ajax Quiz 1.8 SQL Injection — Ajax Quiz 8.2 High 2026-06-19
CVE-2017-20261 Joomla! Component Bargain Product VM3 1.0 SQL Injection — Bargain Product VM3 8.2 High 2026-06-19
CVE-2017-20260 Joomla! Component Price Alert 3.0.2 SQL Injection — Price Alert 8.2 High 2026-06-19
CVE-2017-20259 Joomla OSDownloads 1.7.4 SQL Injection via item view — OSDownloads 8.2 High 2026-06-19
CVE-2017-20258 Joomla! Component RPC Responsive Portfolio 1.6.1 SQL Injection — RPC 8.2 High 2026-06-19
CVE-2017-20257 Joomla! Component Quiz Deluxe 3.7.4 SQL Injection — Quiz Deluxe 8.2 High 2026-06-19
CVE-2017-20256 Joomla Survey Force Deluxe 3.2.4 SQL Injection via invite Parameter — Survey Force Deluxe 8.2 High 2026-06-19
CVE-2017-20255 Joomla! Component JB Visa 1.0 SQL Injection via visatype — JB Visa 8.2 High 2026-06-19
CVE-2017-20254 Joomla! Component User Bench 1.0 SQL Injection via userid — User Bench 8.2 High 2026-06-19
CVE-2017-20253 Joomla! Component My Projects 2.0 SQL Injection — My Projects 8.2 High 2026-06-19
CVE-2017-20252 Joomla NextGen Editor 2.1.0 SQL Injection via plname Parameter — NextGen Editor 8.2 High 2026-06-19
CVE-2026-12045 pgAdmin 4: AI Assistant read-only transaction bypass allows unauthorised writes and remote code execution — pgAdmin 4 9.0 Critical 2026-06-18
CVE-2026-12050 pgAdmin 4: SQL injection in named restore point endpoint — pgAdmin 4 4.3 Medium 2026-06-18
CVE-2026-12044 pgAdmin 4: SQL injection in COMMENT ON ... IS '<description>' rendering across dialog templates — pgAdmin 4 8.8 High 2026-06-18
CVE-2026-56012 WordPress Media LIbrary Assistant plugin <= 3.35 - SQL Injection vulnerability — Media LIbrary Assistant 8.5 High 2026-06-18
CVE-2026-54222 Blind SQL Injection in UBB.threads — UBB.threads - - 2026-06-18
CVE-2026-40455 SQL Injection in LMS — LMS - - 2026-06-18
CVE-2026-54419 PIAF-HMS multiple unauthenticated SQL injection vulnerabilities via mysql_query — PIAF-HMS 9.8 Critical 2026-06-18
CVE-2026-55740 SQL Injection in Nur-Alam39 bus-ticket bus_info.php via busid parameter — bus-ticket 9.8 Critical 2026-06-18
CVE-2026-10736 Tutor LMS <= 3.9.11 - Authenticated (Administrator+) SQL Injection via 'data' Parameter — Tutor LMS – eLearning and online course solution 4.9 Medium 2026-06-18
CVE-2026-11360 Advanced Order Export For WooCommerce <= 4.0.10 - Authenticated (Shop Manager+) SQL Injection via 'sort_direction' Parameter — Advanced Order Export For WooCommerce 4.9 Medium 2026-06-18
CVE-2026-11776 Form Maker by 10Web <= 1.15.43 - Authenticated (Adminsitrator+) SQL Injection via 'groupids' Parameter — Form Maker by 10Web – Mobile-Friendly Drag & Drop Contact Form Builder 4.9 Medium 2026-06-18
CVE-2026-11777 Form Maker by 10Web <= 1.15.43 - Authenticated (Administrator+) SQL Injection via 'name' Parameter — Form Maker by 10Web – Mobile-Friendly Drag & Drop Contact Form Builder 4.9 Medium 2026-06-18
CVE-2026-35069 Dell PowerFlex Manager SQL注入漏洞 — PowerFlex 5.7 Medium 2026-06-17
CVE-2026-35068 Dell PowerFlex Manager SQL注入漏洞 — PowerFlex 3.5 Low 2026-06-17
CVE-2026-54812 WordPress Motors plugin <= 1.4.109 - SQL Injection vulnerability — Motors 9.3 Critical 2026-06-17
CVE-2026-54809 WordPress GIFT4U plugin <= 1.0.10 - SQL Injection vulnerability — GIFT4U 9.3 Critical 2026-06-17

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