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

Goal: 1000 CNY · Raised: 1000 CNY

100.0%

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

9028 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-2025-10047 Email Tracker <= 5.3.15 - Authenticated (Admin+) SQL Injection — Email Tracker 4.9 Medium2025-10-22
CVE-2025-9339 SQL Injection in SIMPLE.ERP — SIMPLE.ERP 7.1AIHighAI2025-10-21
CVE-2025-9428 SQL Injection — Analytics Plus 8.3 High2025-10-21
CVE-2025-26392 SolarWinds Observability Self-Hosted SQL Injection Vulnerability — Observability Self-Hosted 5.4 Medium2025-10-21
CVE-2025-62658 SQL injection in WatchAnalytics through Special:ClearPendingReviews — MediaWiki WatchAnalytics extension 9.8AICriticalAI2025-10-20
CVE-2025-47902 SQL Injection in web resource — Time Provider 4100 9.8AICriticalAI2025-10-20
CVE-2025-41028 SQL injection in Epsilon RH — Epsilon RH 9.8AICriticalAI2025-10-20
CVE-2025-11944 givanz Vvveb Raw SQL import.php import sql injection — Vvveb 4.7 Medium2025-10-19
CVE-2025-11691 PPOM – Product Addons & Custom Fields for WooCommerce <= 33.0.15 - Unauthenticated SQL Injection — PPOM – Product Addons & Custom Fields for WooCommerce 7.5 High2025-10-18
CVE-2025-10187 GSpeech TTS – WordPress Text To Speech Plugin <= 3.17.13 - Authenticated (Admin+) SQL injection — GSpeech TTS – WordPress Text To Speech Plugin 4.9 Medium2025-10-18
CVE-2025-62655 SQL injection in Cargo via Special:CargoExport — MediaWiki Cargo extension 9.8AICriticalAI2025-10-17
CVE-2025-11912 Shenzhen Ruiming Technology Streamax Crocus DeviceState.do Query sql injection — Streamax Crocus 6.3 Medium2025-10-17
CVE-2025-11911 Shenzhen Ruiming Technology Streamax Crocus DeviceFault.do Query sql injection — Streamax Crocus 6.3 Medium2025-10-17
CVE-2025-11910 Shenzhen Ruiming Technology Streamax Crocus MemoryState.do query sql injection — Streamax Crocus 6.3 Medium2025-10-17
CVE-2025-11909 Shenzhen Ruiming Technology Streamax Crocus RepairRecord.do queryLast sql injection — Streamax Crocus 6.3 Medium2025-10-17
CVE-2025-62422 DataEase SQL injection vulnerability — dataease 9.8AICriticalAI2025-10-17
CVE-2025-11904 yanyutao0402 ChanCMS hasUse sql injection — ChanCMS 6.3 Medium2025-10-17
CVE-2025-11903 yanyutao0402 ChanCMS update sql injection — ChanCMS 6.3 Medium2025-10-17
CVE-2025-11902 yanyutao0402 ChanCMS findField sql injection — ChanCMS 6.3 Medium2025-10-17
CVE-2025-62423 ClipBucket V5 Blind SQL injection in the Admin Panel — clipbucket-v5 6.7 Medium2025-10-16
CVE-2025-41019 SQL injection vulnerability in Sergestec's Exito — SISTICK 9.8AICriticalAI2025-10-16
CVE-2025-41018 SQL injection vulnerability in Sergestec's Exito — Exito 9.8AICriticalAI2025-10-16
CVE-2025-10682 TARIFFUXX <= 1.4 - Authenticated (Contributor+) SQL Injection via tariffuxx_configurator Shortcode — TARIFFUXX 6.5 Medium2025-10-15
CVE-2025-11365 WP Google Map Plugin <= 1.0 - Authenticated (Contributor+) SQL Injection — WP Google Map Plugin 6.5 Medium2025-10-15
CVE-2025-10743 Outdoor <= 1.3.2 - Unauthenticated SQL Injection — Outdoor 7.5 High2025-10-15
CVE-2025-11177 External Login <= 1.11.2 - Unauthenticated SQL Injection via log — External Login 7.5 High2025-10-15
CVE-2025-10575 WP jQuery Pager <= 1.4.0 - Authenticated (Contributor+) SQL Injection via Shortcode — WP jQuery Pager 6.5 Medium2025-10-15
CVE-2025-10310 Rich Snippet Site Report <= 2.0.0105 - Authenticated (Admin+) SQL Injection — Rich Snippet Site Report 4.9 Medium2025-10-15
CVE-2025-10045 onOffice for WP-Websites <= 6.5.1 - Authenticated (Editor+) SQL Injection — onOffice for WP-Websites 4.9 Medium2025-10-15
CVE-2025-10730 Wp tabber widget <= 4.0 - Authenticated (Contributor+) SQL Injection — Wp tabber widget 6.5 Medium2025-10-15

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