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

Goal: 1000 CNY · Raised: 1000 CNY

100.0%

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

8957 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, AvailabilityExecute 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.
ConfidentialityRead Application Data
Since SQL databases generally hold sensitive data, loss of confidentiality is a frequent problem with SQL injection vulnerabilities.
AuthenticationGain 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 ControlBypass 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.
IntegrityModify 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 DesignUse 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 DesignIf 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, OperationRun 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 DesignFor 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.
ImplementationWhile 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 IDTitleCVSSSeverityPublished
CVE-2018-25166 Meneame English Pligg 5.8 SQL Injection via search Parameter — Meneame English Pligg 8.2 High2026-03-06
CVE-2018-25165 Galaxy Forces MMORPG 0.5.8 SQL Injection via ads.php — Galaxy Forces MMORPG 7.1 High2026-03-06
CVE-2018-25163 BitZoom 1.0 SQL Injection via rollno Parameter — BitZoom 8.2 High2026-03-06
CVE-2018-25161 Warranty Tracking System 11.06.3 SQL Injection via SearchCustomer.php — Warranty Tracking System 8.2 High2026-03-06
CVE-2026-28438 CocoIndex Doris target connector didn't verify table name when constructing ALTER TABLE statements — cocoindex 8.8 -2026-03-06
CVE-2026-28785 Ghostfolio: Time-Based Blind SQL Injection in Manual Asset Import — ghostfolio 8.8 -2026-03-06
CVE-2026-27005 Chartbrew: SQL injection in date-type variable handling (applyMysqlOrPostgresVariables) — chartbrew 9.1 -2026-03-06
CVE-2026-28501 WWBN AVideo: Unauthenticated SQL Injection via JSON Request Bypass in objects/videos.json.php — AVideo 9.8 Critical2026-03-06
CVE-2026-3616 DefaultFuction Jeson Customer Relationship Management System edit.php sql injection — Jeson Customer Relationship Management System 6.3 Medium2026-03-06
CVE-2026-28443 OpenReplay: SQL injection in cards/search via unvalidated sort field parameter — openreplay 9.8 -2026-03-05
CVE-2026-29081 Frappe: Possibility of SQL Injection due to improper fieldname sanitization — frappe 6.5 Medium2026-03-05
CVE-2026-28284 FreePBX: Authenticated SQL Injection Vulnerabilities in FreePBX Logfiles Module — security-reporting 8.8 -2026-03-05
CVE-2026-28210 FreePBX: Authenticated SQL Injection in CDR (Call Data Record) Reports — security-reporting 8.8 -2026-03-05
CVE-2026-2893 Page and Post Clone <= 6.3 - Authenticated (Contributor+) SQL Injection via 'meta_key' Parameter — Fast Page & Post Duplicator 6.5 Medium2026-03-05
CVE-2026-28115 WordPress WP Attractive Donations System - Easy Stripe & Paypal donations plugin <= 1.25 - SQL Injection vulnerability — WP Attractive Donations System - Easy Stripe & Paypal donations 9.3 Critical2026-03-05
CVE-2026-27428 WordPress Eagle Booking plugin <= 1.3.4.3 - SQL Injection vulnerability — Eagle Booking 8.5 High2026-03-05
CVE-2026-27373 WordPress Tablesome plugin <= 1.2.3 - SQL Injection vulnerability — Tablesome 8.5 High2026-03-05
CVE-2025-69338 WordPress Riode Core plugin <= 1.6.26 - SQL Injection vulnerability — Riode Core 9.3 Critical2026-03-05
CVE-2026-3523 Apocalypse Meow <= 22.1.0 - Authenticated (Administrator+) SQL Injection via 'type' Parameter — Apocalypse Meow 4.9 Medium2026-03-05
CVE-2026-20003 Cisco Secure Firewall Management Center SQL注入漏洞 — Cisco Secure Firewall Management Center (FMC) 4.9 Medium2026-03-04
CVE-2026-20002 Cisco Secure Firewall Management Center SQL注入漏洞 — Cisco Secure Firewall Management Center (FMC) 8.1 High2026-03-04
CVE-2019-25507 Ashop Shopping Cart Software Lastest SQL Injection via index.php — Ashop Shopping Cart Software 8.2 High2026-03-04
CVE-2019-25506 FreeSMS 2.1.2 Authentication Bypass via SQL Injection — FreeSMS 8.2 High2026-03-04
CVE-2019-25504 NCrypted Jobgator Lastest SQL Injection via agents Find-Jobs — NCrypted Jobgator 8.2 High2026-03-04
CVE-2019-25505 Tradebox 5.4 SQL Injection via symbol Parameter — Tradebox 7.1 High2026-03-04
CVE-2019-25503 PHPads 2.0 SQL Injection via click.php3 bannerID — PHPads 7.1 High2026-03-04
CVE-2019-25501 Simple Job Script SQL Injection via delete_application_ajax.php — Simple Job Script 8.2 High2026-03-04
CVE-2019-25500 Simple Job Script SQL Injection via register-recruiters endpoint — Simple Job Script 8.2 High2026-03-04
CVE-2019-25499 Simple Job Script SQL Injection via get_job_applications_ajax.php — Simple Job Script 8.2 High2026-03-04
CVE-2019-25498 Simple Job Script SQL Injection via searched Endpoint — Simple Job Script 8.2 High2026-03-04

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