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

Goal: 1000 CNY · Raised: 1325 CNY

100%

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

9481 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-2019-25761 Joomla! Component JoomCRM 1.1.1 SQL Injection via deal_id — JoomCRM 7.1 High2026-06-19
CVE-2019-25759 Joomla! Component vBizz 1.0.7 SQL Injection — vBizz 7.1 High2026-06-19
CVE-2019-25757 Joomla vWishlist 1.0.1 SQL Injection via vproductid Parameter — vWishlist 7.1 High2026-06-19
CVE-2019-25756 Joomla! Component vAccount 2.0.2 SQL Injection via vaccount-dashboard — vAccount 8.2 High2026-06-19
CVE-2019-25755 Joomla vReview 1.9.11 SQL Injection via editReview — vReview 8.2 High2026-06-19
CVE-2019-25754 Joomla vRestaurant 1.9.4 SQL Injection via menu-listing-layout — vRestaurant 8.2 High2026-06-19
CVE-2019-25753 Joomla! Component VMap 1.9.6 SQL Injection via loadmarker — VMap 8.2 High2026-06-19
CVE-2019-25752 Joomla! Component J-BusinessDirectory 4.9.7 SQL Injection — J-BusinessDirectory 8.2 High2026-06-19
CVE-2019-25751 Joomla J-ClassifiedsManager 3.0.5 SQL Injection — ClassifiedsManager 8.2 High2026-06-19
CVE-2019-25750 Joomla J-MultipleHotelReservation 6.0.7 SQL Injection — MultipleHotelReservation 8.2 High2026-06-19
CVE-2019-25749 Joomla J-CruisePortal 6.0.4 SQL Injection via cruises — J-CruisePortal 7.1 High2026-06-19
CVE-2019-25748 Joomla JHotelReservation 6.0.7 SQL Injection via search-hotels — JHotelReservation 8.2 High2026-06-19
CVE-2017-20282 Joomla! Component jCart for OpenCart 2.0 SQL Injection — jCart for OpenCart 8.2 High2026-06-19
CVE-2017-20281 Joomla! Component Extra Search 2.2.8 SQL Injection — Extra Search 8.2 High2026-06-19
CVE-2017-20280 Joomla Component Myportfolio 3.0.2 SQL Injection via pid Parameter — Myportfolio 8.2 High2026-06-19
CVE-2017-20279 Joomla Payage 2.05 SQL Injection via aid Parameter — Joomla Payage 8.2 High2026-06-19
CVE-2017-20278 Joomla JoomRecipe 1.0.3 SQL Injection via category parameter — JoomRecipe 8.2 High2026-06-19
CVE-2017-20277 Joomla JoomRecipe 1.0.4 Component Blind SQL Injection via search_author — Joomla JoomRecipe 8.2 High2026-06-19
CVE-2017-20276 Joomla! Component SIMGenealogy 2.1.5 SQL Injection — SIMGenealogy 8.2 High2026-06-19
CVE-2017-20275 Joomla! Component PHP-Bridge 1.2.3 SQL Injection via id Parameter — Bridge 8.2 High2026-06-19
CVE-2017-20274 Joomla LMS King Professional 3.2.4.0 SQL Injection via learningpath — LMS King Professional 8.2 High2026-06-19
CVE-2017-20273 Joomla Event Registration Pro Calendar 4.1.3 SQL Injection — Event Registration Pro Calendar 8.2 High2026-06-19
CVE-2017-20272 Joomla Ultimate Property Listing 1.0.2 SQL Injection via sf_selectuser_id — Ultimate Property Listing 8.2 High2026-06-19
CVE-2017-20271 Joomla StreetGuessr Game 1.1.8 SQL Injection via catid — StreetGuessr Game 8.2 High2026-06-19
CVE-2017-20270 Joomla! Component Twitch Tv 1.1 SQL Injection — Twitch Tv 8.2 High2026-06-19
CVE-2017-20269 Joomla! Component KissGallery 1.0.0 SQL Injection — KissGallery 8.2 High2026-06-19
CVE-2017-20268 Joomla! Component Zap Calendar Lite 4.3.4 SQL Injection — Zap Calendar Lite 8.2 High2026-06-19
CVE-2017-20267 Joomla! Component Calendar Planner 1.0.1 SQL Injection — Calendar Planner 8.2 High2026-06-19
CVE-2017-20266 Joomla SP Movie Database 1.3 SQL Injection via searchword — SP Movie Database 8.2 High2026-06-19
CVE-2017-20265 Joomla! Component Flip Wall 8.0 SQL Injection — Flip Wall 7.1 High2026-06-19

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