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

Goal: 1000 CNY · Raised: 1000 CNY

100.0%

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

9025 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-12252 code-projects Online Event Judging System action.php sql injection — Online Event Judging System 6.3 Medium2025-10-27
CVE-2025-12248 CLTPHP search.html sql injection — CLTPHP 7.3 High2025-10-27
CVE-2025-12243 code-projects Client Details System GET Parameter welcome.php sql injection — Client Details System 6.3 Medium2025-10-27
CVE-2025-12242 CodeAstro Gym Management System check-attendance.php sql injection — Gym Management System 6.3 Medium2025-10-27
CVE-2025-12238 code-projects Automated Voting System user.php sql injection — Automated Voting System 6.3 Medium2025-10-27
CVE-2025-12237 projectworlds Advanced Library Management System index.php sql injection — Advanced Library Management System 7.3 High2025-10-27
CVE-2025-12226 SourceCodester Best House Rental Management System admin_class.php save_house sql injection — Best House Rental Management System 4.7 Medium2025-10-27
CVE-2025-12215 projectworlds Online Shopping System login_submit.php sql injection — Online Shopping System 7.3 High2025-10-27
CVE-2025-12208 SourceCodester Best House Rental Management System admin_class.php login2 sql injection — Best House Rental Management System 7.3 High2025-10-27
CVE-2025-8709 SQL Injection in langchain-ai/langchain — langchain-ai/langchain 9.8 -2025-10-26
CVE-2025-8416 Product Filter by WBW <= 2.9.7 - Unauthenticated SQL Injection — Product Filter for WooCommerce by WBW 7.5 High2025-10-25
CVE-2025-4203 wpForo Forum <= 2.4.8 - Unauthenticated SQL Injection via get_members Function — wpForo Forum 7.5 High2025-10-25
CVE-2025-9322 Stripe Payment Forms <= 8.3.1 - Unauthenticated SQL Injection — Stripe Payment Forms by WP Full Pay – Accept Credit Card Payments, Donations & Subscriptions 7.5 High2025-10-25
CVE-2025-11893 Charitable – Donation Plugin for WordPress – Fundraising with Recurring Donations & More <= 1.8.8.4 - Authenticated (Subscriber+) SQL Injection — Charitable – Donation Plugin for WordPress – Fundraising with Recurring Donations & More 6.5 Medium2025-10-25
CVE-2025-8536 SQL Injection in DobryCMS — DobryCMS 9.8 -2025-10-24
CVE-2025-11253 SQLi in Aksis Technologies' Netty ERP — Netty ERP 9.8 Critical2025-10-24
CVE-2025-10748 RapidResult <= 1.2 - Authenticated (Contributor+) SQL Injection — RapidResult 6.5 Medium2025-10-24
CVE-2025-10740 URL Shortener Plugin For WordPress <= 3.0.7 - Missing Authorization to Authenticated (Subscriber+) Link Manipulation — URL Shortener Plugin For WordPress 6.3 Medium2025-10-24
CVE-2025-62617 Admidio Vulnerable to Authenticated SQL Injection in Member Assignment Functionality — admidio 7.2 High2025-10-22
CVE-2025-62606 my little forum vulnerable to SQL Injection in Bookmark Reordering via bookmarks parameter — mylittleforum 8.8 High2025-10-22
CVE-2025-62015 WordPress Advanced Coupons for WooCommerce Coupons plugin <= 4.6.8 - SQL Injection vulnerability — Advanced Coupons for WooCommerce Coupons 7.6 High2025-10-22
CVE-2025-59557 WordPress Learts Addons Plugin < 1.7.5 - SQL Injection Vulnerability — Learts Addons 9.3 Critical2025-10-22
CVE-2025-49931 WordPress JetSearch plugin <= 3.5.10 - SQL Injection vulnerability — JetSearch 9.3 Critical2025-10-22
CVE-2025-49915 WordPress SMS Alert Order Notifications plugin <= 3.8.5 - SQL Injection vulnerability — SMS Alert Order Notifications 9.3 Critical2025-10-22
CVE-2025-49378 WordPress Hydra Booking plugin <= 1.1.10 - SQL Injection vulnerability — Hydra Booking 8.5 High2025-10-22
CVE-2025-48091 WordPress AnyComment plugin <= 0.3.6 - SQL Injection vulnerability — AnyComment 8.5 High2025-10-22
CVE-2025-57870 BUG-000179884 - There is a security vulnerability in ArcGIS Server Feature Services. — ArcGIS Server 10.0 Critical2025-10-22
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

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