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-22484 WordPress Lisfinity Core plugin <= 1.5.0 - SQL Injection vulnerability — Lisfinity Core 9.3 Critical2026-03-25
CVE-2024-58341 OpenCart Core 4.0.2.3 SQL Injection via search Parameter — OpenCart Core 8.2 High2026-03-25
CVE-2026-4815 SQL Injection vulnerability in Support Board — Support Board 8.8 -2026-03-25
CVE-2026-4784 code-projects Simple Laundry System Parameter checkcheckout.php sql injection — Simple Laundry System 7.3 High2026-03-25
CVE-2026-4783 itsourcecode College Management System Parameter add-single-student-results.php sql injection — College Management System 6.3 Medium2026-03-25
CVE-2026-4781 SourceCodester Sales and Inventory System HTTP GET Parameter update_purchase.php sql injection — Sales and Inventory System 6.3 Medium2026-03-24
CVE-2026-4780 SourceCodester Sales and Inventory System HTTP GET Parameter update_out_standing.php sql injection — Sales and Inventory System 6.3 Medium2026-03-24
CVE-2026-4779 SourceCodester Sales and Inventory System HTTP GET Parameter update_customer_details.php sql injection — Sales and Inventory System 6.3 Medium2026-03-24
CVE-2026-4778 SourceCodester Sales and Inventory System HTTP GET Parameter update_category.php sql injection — Sales and Inventory System 6.3 Medium2026-03-24
CVE-2026-4777 SourceCodester Sales and Inventory System POST Parameter view_supplier.php sql injection — Sales and Inventory System 6.3 Medium2026-03-24
CVE-2026-23921 Blind, read-only SQL injection in Zabbix API via sortfield parameter — Zabbix 8.8 -2026-03-24
CVE-2026-33539 Parse Server: SQL injection via aggregate and distinct field names in PostgreSQL adapter — parse-server 7.2 -2026-03-24
CVE-2019-25642 Bootstrapy CMS Lastest Multiple SQL Injection via Forum and Contact Modules — Bootstrapy CMS 8.2 High2026-03-24
CVE-2019-25643 eNdonesia Portal v8.7 SQL Injection via banners.php — eNdonesia Portal 8.2 High2026-03-24
CVE-2019-25641 Netartmedia Vlog System Lastest SQL Injection via email Parameter — Netartmedia Vlog System 8.2 High2026-03-24
CVE-2019-25640 Inout Article Base CMS Lastest SQL Injection via portalLogin.php — Inout Article Base CMS 8.2 High2026-03-24
CVE-2019-25639 Matrimony Website Script M-Plus Multiple SQL Injection — Matrimony Website Script 8.2 High2026-03-24
CVE-2019-25638 Meeplace Business Review Script Lastest SQL Injection via addclick.php — Meeplace Business Review Script 7.1 High2026-03-24
CVE-2019-25636 Zeeways Jobsite CMS Lastest SQL Injection via id Parameter — Zeeways Jobsite CMS 8.2 High2026-03-24
CVE-2019-25635 Zeeways Matrimony CMS Lastest SQL Injection via profile_list — Zeeways Matrimony CMS 8.2 High2026-03-24
CVE-2026-4662 JetEngine <= 3.8.6.1 - Unauthenticated SQL Injection via Listing Grid 'filtered_query' Parameter — JetEngine 7.5 High2026-03-24
CVE-2026-4632 itsourcecode Online Enrollment System Parameter index.php sql injection — Online Enrollment System 7.3 High2026-03-24
CVE-2026-4625 SourceCodester Online Admission System programmes.php sql injection — Online Admission System 7.3 High2026-03-24
CVE-2026-4624 SourceCodester Online Library Management System Parameter home.php sql injection — Online Library Management System 7.3 High2026-03-24
CVE-2026-3079 LearnDash LMS <= 5.0.3 - Authenticated (Contributor+) SQL Injection via 'filters[orderby_order]' Parameter — LearnDash LMS 6.5 Medium2026-03-24
CVE-2026-4615 SourceCodester Online Catering Reservation search.php sql injection — Online Catering Reservation 7.3 High2026-03-23
CVE-2026-4614 itsourcecode sanitize or validate this input Parameter subjects.php sql injection — sanitize or validate this input 6.3 Medium2026-03-23
CVE-2026-4613 SourceCodester E-Commerce Site products.php sql injection — E-Commerce Site 7.3 High2026-03-23
CVE-2026-2412 Quiz and Survey Master (QSM) <= 10.3.5 - Authenticated (Contributor+) SQL Injection via 'merged_question' Parameter — Quiz and Survey Master (QSM) – Easy Quiz and Survey Maker 6.5 Medium2026-03-23
CVE-2026-4306 WP Job Portal <= 2.4.8 - Unauthenticated SQL Injection via 'radius' Parameter — WP Job Portal – AI-Powered Recruitment System for Company or Job Board website 7.5 High2026-03-23

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