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

Goal: 1000 CNY · Raised: 1000 CNY

100.0%

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

8951 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-42287 Emlog: SQL Injection Vulnerability in log_model.php within addLog() and updateLog() Functions — emlog--2026-05-08
CVE-2026-41889 pgx: SQL Injection via placeholder confusion with dollar quoted string literals — pgx--2026-05-08
CVE-2026-41496 PraisonAI: SQL Injection via unvalidated `table_prefix` in 9 conversation store backends (incomplete fix for CVE-2026-40315) — PraisonAI 8.1 High2026-05-08
CVE-2026-42208 LiteLLM: SQL injection in Proxy API key verification — litellm--2026-05-08
CVE-2026-8133 zyx0814 FilePress Shares Filelist API admin.php sql injection — FilePress 7.3 High2026-05-08
CVE-2026-8132 CodeAstro Leave Management System login.php sql injection — Leave Management System 7.3 High2026-05-08
CVE-2026-8131 SourceCodester SUP Online Shopping replymsg.php sql injection — SUP Online Shopping 7.3 High2026-05-08
CVE-2026-8130 SourceCodester SUP Online Shopping message.php sql injection — SUP Online Shopping 7.3 High2026-05-08
CVE-2026-8129 SourceCodester SUP Online Shopping wishlist.php sql injection — SUP Online Shopping 7.3 High2026-05-08
CVE-2026-8128 SourceCodester SUP Online Shopping viewmsg.php sql injection — SUP Online Shopping 7.3 High2026-05-08
CVE-2026-8126 SourceCodester Comment System post_comment.php sql injection — Comment System 7.3 High2026-05-08
CVE-2026-8125 code-projects Simple Chat System sendMessage.php sql injection — Simple Chat System 6.3 Medium2026-05-08
CVE-2026-8114 JeecgBoot JSON Object loadTreeData sql injection — JeecgBoot 6.3 Medium2026-05-07
CVE-2026-8098 code-projects Feedback System checklogin.php sql injection — Feedback System 7.3 High2026-05-07
CVE-2026-8097 CodeAstro Online Classroom askquery.php sql injection — Online Classroom 6.3 Medium2026-05-07
CVE-2026-8083 SourceCodester Pharmacy Sales and Inventory System ajax.php save_user sql injection — Pharmacy Sales and Inventory System 7.3 High2026-05-07
CVE-2026-44349 Daptin fuzzy search injects unvalidated column name into raw SQL — daptin--2026-05-07
CVE-2026-41422 Daptin vulnerable to SQL injection via unvalidated goqu.L() calls in aggregate API — daptin 8.3 High2026-05-07
CVE-2026-41490 Dagster Vulnerable to SQL Injection via Dynamic Partition Keys in Database I/O Manager Integrations — dagster 8.3 High2026-05-07
CVE-2025-68060 WordPress Team Member plugin <= 8.5 - SQL Injection vulnerability — Team Member 7.6 High2026-05-07
CVE-2026-41143 YesWiki vulnerable to authenticated SQL Injection via id_fiche in EntryManager::formatDataBeforeSave() — yeswiki 8.8 High2026-05-07
CVE-2026-4348 BetterDocs Pro <= 3.7.0 - Unauthenticated SQL Injection via Encyclopedia 'limit' Parameter — BetterDocs Pro 7.5 High2026-05-07
CVE-2026-41641 NocoBase Vulnerable to SQL Validation Bypass via `sqlCollection:update` Missing `checkSQL` Call — nocobase 7.2 High2026-05-07
CVE-2026-41640 NocoBase Vulnerable to SQL Injection via String Concatenation in Recursive Eager Loading — nocobase 7.5 High2026-05-07
CVE-2026-29090 Rucio SQL injection in postgres_meta DID search path compromises PostgreSQL metadata database — rucio--2026-05-06
CVE-2026-29080 Rucio SQL Injection in FilterEngine Oracle JSON Path via DID Search API — rucio--2026-05-06
CVE-2026-1719 Gravity Bookings <= 2.5.9 - Unauthenticated SQL Injection via 'category_id' Parameter — Gravity Bookings 7.5 High2026-05-06
CVE-2026-40331 Masa CMS unauthenticated SQL injection via altTable parameter in JSON API — MasaCMS--2026-05-05
CVE-2026-40330 Masa CMS SQL injection via sortDirection parameter in beanFeed — MasaCMS--2026-05-05
CVE-2026-40329 SQL Injection vulnerability via sortBy in beanFeed — MasaCMS--2026-05-05

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