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-22196 GestSup < 3.2.60 SQL Injection in Ticket Creation — GestSup 8.1 -2026-01-09
CVE-2026-22197 GestSup < 3.2.60 Multiple SQL Injections in Asset List — GestSup 8.1 -2026-01-09
CVE-2026-22195 GestSup < 3.2.60 SQL Injection in Search Bar — GestSup 8.8 -2026-01-09
CVE-2025-15492 RainyGao DocSys GroupMemberMapper.xml sql injection — DocSys 6.3 Medium2026-01-09
CVE-2026-0803 PHPGurukul Online Course Registration System enroll.php sql injection — Online Course Registration System 6.3 Medium2026-01-09
CVE-2026-0733 PHPGurukul Online Course Registration System manage-students.php sql injection — Online Course Registration System 6.3 Medium2026-01-08
CVE-2026-0729 code-projects Intern Membership Management System add_activity.php sql injection — Intern Membership Management System 4.7 Medium2026-01-08
CVE-2026-0728 code-projects Intern Membership Management System delete_admin.php sql injection — Intern Membership Management System 4.7 Medium2026-01-08
CVE-2026-21892 Parsl Monitoring Visualization Vulnerable to SQL Injection — parsl 5.3 Medium2026-01-08
CVE-2025-67928 WordPress Automotive Listings plugin <= 18.6 - SQL Injection vulnerability — Automotive Listings 9.3 Critical2026-01-08
CVE-2025-67921 WordPress Lobo theme < 2.8.6 - SQL Injection vulnerability — Lobo 8.5 High2026-01-08
CVE-2025-22728 WordPress Workreap (theme's plugin) plugin <= 3.3.6 - SQL Injection vulnerability — Workreap (theme's plugin) 8.5 High2026-01-08
CVE-2025-23993 WordPress Felan Framework plugin <= 1.1.3 - SQL Injection vulnerability — Felan Framework 9.3 Critical2026-01-08
CVE-2025-22713 WordPress WooCommerce Orders & Customers Exporter plugin <= 5.4 - SQL Injection vulnerability — WooCommerce Orders & Customers Exporter 8.5 High2026-01-08
CVE-2026-0701 code-projects Intern Membership Management System add_admin.php sql injection — Intern Membership Management System 4.7 Medium2026-01-08
CVE-2026-0700 code-projects Intern Membership Management System check_admin.php sql injection — Intern Membership Management System 7.3 High2026-01-08
CVE-2026-0699 code-projects Intern Membership Management System edit_activity.php sql injection — Intern Membership Management System 4.7 Medium2026-01-08
CVE-2026-0698 code-projects Intern Membership Management System edit_students.php sql injection — Intern Membership Management System 4.7 Medium2026-01-08
CVE-2026-0697 code-projects Intern Membership Management System edit_admin.php sql injection — Intern Membership Management System 4.7 Medium2026-01-08
CVE-2026-21875 ClipBucket v5 Vulnerable to Blind SQL Injection through Channel Comments — clipbucket-v5 9.8 Critical2026-01-07
CVE-2023-7333 bluelabsio records-mover Table Object sql injection — records-mover 5.3 Medium2026-01-07
CVE-2026-21856 Tarkov Data Manager has Authenticated SQL Injection — tarkov-data-manager 7.2 High2026-01-07
CVE-2025-32303 WordPress WPCHURCH plugin <= 2.7.0 - SQL Injection Vulnerability — WPCHURCH 9.3 Critical2026-01-07
CVE-2025-69351 WordPress Ninja Tables plugin <= 5.2.4 - SQL Injection vulnerability — Ninja Tables 8.5 High2026-01-06
CVE-2025-9318 Quiz and Survey Master (QSM) <= 10.3.1 - Authenticated (Subscriber+) SQL Injection via `is_linking` Query Parameter — Quiz and Survey Master (QSM) – Easy Quiz and Survey Maker 6.5 Medium2026-01-06
CVE-2025-14153 Page Expire Popup/Redirection for WordPress <= 1.0 - Authenticated (Author+) SQL Injection via 'id' Shortcode Attribute — Page Expire Popup/Redirection for WordPress 6.5 Medium2026-01-06
CVE-2025-13652 CBX Bookmark & Favorite <= 2.0.4 - Authenticated (Subscriber+) SQL Injection via `orderby` Parameter — CBX Bookmark & Favorite 6.5 Medium2026-01-06
CVE-2025-13409 Form Vibes – Database Manager for Forms <= 1.4.13 - Authenticated (Admin+) SQL Injection — Form Vibes – Database Manager for Forms 4.9 Medium2026-01-06
CVE-2026-0607 code-projects Online Music Site AdminViewSongs.php sql injection — Online Music Site 7.3 High2026-01-05
CVE-2026-0606 code-projects Online Music Site Albums.php sql injection — Online Music Site 7.3 High2026-01-05

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