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-2026-20001 Cisco Secure Firewall Management Center Software SQL Injection Vulnerabilities — Cisco Secure Firewall Management Center (FMC) 6.5 Medium2026-03-04
CVE-2023-7337 JS Help Desk – AI-Powered Support & Ticketing System 2.8.2 - Unauthenticated SQL Injection via 'js-support-ticket-token-tkstatus' Cookie — JS Help Desk – AI-Powered Support & Ticketing System 7.5 High2026-03-04
CVE-2026-2363 WP-Members Membership Plugin <= 3.5.5.1 - Authenticated (Contributor+) SQL Injection via 'order_by' Shortcode Attribute — WP-Members Membership Plugin 6.5 Medium2026-03-04
CVE-2026-1651 Email Subscribers & Newsletters <= 5.9.16 - Authenticated (Administrator+) SQL Injection via 'workflow_ids' Parameter — Email Subscribers & Newsletters – Email Marketing, Post Notifications & Newsletter Plugin for WordPress 6.5 Medium2026-03-04
CVE-2026-3487 itsourcecode College Management System class-result.php sql injection — College Management System 4.7 Medium2026-03-03
CVE-2026-3486 itsourcecode College Management System student-fee.php sql injection — College Management System 4.7 Medium2026-03-03
CVE-2026-1487 LatePoint <= 5.2.7 - Authenticated (Administrator+) SQL Injection via JSON Import — LatePoint – Calendar Booking Plugin for Appointments and Events 6.5 Medium2026-03-03
CVE-2026-3180 Contest Gallery <= 28.1.4 - Unauthenticated SQL Injection — Contest Gallery – Upload & Vote Photos, Media, Sell with PayPal & Stripe 7.5 High2026-03-02
CVE-2026-28399 NocoDB: SQL Injection via DATEADD Formula — nocodb 8.8AIHighAI2026-03-02
CVE-2025-50192 Chamilo: Time-based SQL Injection in /main/webservices/registration.soap.php — chamilo-lms 9.8AICriticalAI2026-03-02
CVE-2025-50191 Chamilo: Error-based SQL Injection via POST userFile with the /main/exercise/hotpotatoes.php script — chamilo-lms 9.8AICriticalAI2026-03-02
CVE-2025-50190 Chamilo: Error-based SQL Injection via GET openid.assoc_handle with the /index.php script — chamilo-lms 9.8AICriticalAI2026-03-02
CVE-2025-50189 Chamilo: Error-based SQL Injection — chamilo-lms 9.8AICriticalAI2026-03-02
CVE-2025-50188 Error-based SQL Injection in Chamilo LMS — chamilo-lms 9.8AICriticalAI2026-03-02
CVE-2025-12462 Blind SQL Injection in DobryCMS — DobryCMS 9.8AICriticalAI2026-03-02
CVE-2025-30062 SQL injection in CheckUnitCodeAndKey.pl — CGM CLININET 9.8AICriticalAI2026-03-02
CVE-2025-10350 SQL injection in CGM NETRAAD — CGM NETRAAD 6.5AIMediumAI2026-03-02
CVE-2026-2584 SQL Injection in Ciser System SL firmware — CSIP firmware 5.3AIMediumAI2026-03-02
CVE-2026-3413 itsourcecode University Management System admin_single_student.php sql injection — University Management System 7.3 High2026-03-02
CVE-2026-3411 itsourcecode University Management System admin_single_student_update.php sql injection — University Management System 7.3 High2026-03-02
CVE-2026-3410 itsourcecode Society Management System check_studid.php sql injection — Society Management System 7.3 High2026-03-02
CVE-2026-3406 projectworlds Online Art Gallery Shop Registration registration.php sql injection — Online Art Gallery Shop 7.3 High2026-03-02
CVE-2026-28562 wpForo Forum 2.4.14 SQL Injection via Topics ORDER BY Parameter — wpForo Forum 8.2 High2026-02-28
CVE-2025-13673 Tutor LMS <= 3.9.6 - Unauthenticated SQL Injection via coupon_code — Tutor LMS – eLearning and online course solution 7.5 High2026-02-28
CVE-2026-28516 openDCIM <= 23.04 SQL Injection in Config::UpdateParameter — openDCIM 8.8 -2026-02-27
CVE-2026-27832 Group-Office Has Authenticated SQL Injection in advancedQueryData.comparator — groupoffice 8.8 -2026-02-27
CVE-2019-25497 osCommerce 2.3.4.1 SQL Injection via currency Parameter — osCommerce 8.2 High2026-02-27
CVE-2019-25496 osCommerce 2.3.4.1 SQL Injection via products_id Parameter — osCommerce 8.2 High2026-02-27
CVE-2019-25495 osCommerce 2.3.4.1 SQL Injection via reviews_id Parameter — osCommerce 8.2 High2026-02-27
CVE-2019-25494 Homey BNB V4 SQL Injection Authentication Bypass via Admin Panel — Homey BNB (Airbnb Clone Script) 8.2 High2026-02-27

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