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-2663 Alixhan xh-admin-backend Database Query query sql injection — xh-admin-backend 6.3 Medium2026-02-18
CVE-2025-59920 SQL injection in time@work from systems@work — time at work 8.8AIHighAI2026-02-18
CVE-2026-1317 WP Import – Ultimate CSV XML Importer for WordPress <= 7.37 - Authenticated (Subscriber+) SQL Injection via File Name — WP Ultimate CSV Importer – Import CSV, XML & Excel into WordPress 6.5 Medium2026-02-18
CVE-2025-8781 Bookster – WordPress Appointment Booking Plugin <= 2.1.1 - Authenticated (Administrator+) SQL Injection via 'raw' — Bookster – WordPress Appointment Booking Plugin 4.9 Medium2026-02-18
CVE-2026-2495 WPNakama <= 0.6.5 - Unauthenticated SQL Injection via 'order' REST API Parameter — WPNakama – Team and multi-Client Collaboration, Editorial and Project Management 7.5 High2026-02-18
CVE-2026-1639 Taskbuilder <= 5.0.2 - Authenticated (Subscriber+) SQL Injection via 'order' and 'sort_by' Parameters — Taskbuilder – Project Management & Task Management Tool With Kanban Board 6.5 Medium2026-02-18
CVE-2026-2576 Business Directory Plugin <= 6.4.21 - Unauthenticated SQL Injection via payment Parameter — Business Directory Plugin – Easy Listing Directories for WordPress 7.5 High2026-02-18
CVE-2026-2621 Sciyon Koyuan Thermoelectricity Heat Network Management System AsyncTreeProxy.aspx sql injection — Koyuan Thermoelectricity Heat Network Management System 7.3 High2026-02-17
CVE-2026-2620 Huace Monitoring and Early Warning System ProjectRole.aspx sql injection — Monitoring and Early Warning System 7.3 High2026-02-17
CVE-2025-7631 Time-Based Blind SQLi in Tumeva Internet Technologies' Tumeva Prime News Software — Tumeva Prime News Software 8.6 High2026-02-17
CVE-2026-2247 SQL Injection in Clickedu's SaaS platform — SaaS platform 8.8AIHighAI2026-02-17
CVE-2026-2553 tushar-2223 Hotel-Management-System HTTP POST Request home.php sql injection — Hotel-Management-System 6.3 Medium2026-02-16
CVE-2026-1258 Mail Mint <= 1.19.2 - Authenticated (Administrator+) SQL Injection via Multiple API Endpoints — Mail Mint – Email Marketing, Newsletter, Email Automation & WooCommerce Emails 4.9 Medium2026-02-14
CVE-2026-2024 PhotoStack Gallery <= 0.4.1 - Unauthenticated SQL Injection via 'postid' Parameter — PhotoStack Gallery 7.5 High2026-02-14
CVE-2019-25335 PRO-7070 Hazır Profesyonel Web Sitesi 1.0 - Authentication Bypass — 7070 Hazır Profesyonel Web Sitesi 7.5 High2026-02-12
CVE-2019-25325 Thrive Smart Home 1.1 - 'Smart Home' Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') — Smart Home 8.2 High2026-02-12
CVE-2019-25320 elearning-script 1.0 - Authentication Bypass — elearning-script 6.5 Medium2026-02-12
CVE-2019-25347 thesystem App 1.0 - 'username' SQL Injection — thesystem 7.5 High2026-02-12
CVE-2019-25346 thesystem 1.0 - 'server_name' SQL Injection — thesystem 7.5 High2026-02-12
CVE-2026-22821 mreporting affected by a SQLI on date change — mreporting 4.9 Medium2026-02-12
CVE-2025-10969 SQLi in Farktor Software's E-Commerce Package — E-Commerce Package 9.8 Critical2026-02-12
CVE-2025-13431 SlimStat Analytics <= 5.3.1 - Authenticated (Subscriber+) SQL Injection via `args` Parameter — SlimStat Analytics 6.5 Medium2026-02-11
CVE-2026-25993 EverShop has a Second-Order SQL Injection in URL Rewrite Processing Derived from Category URL Keys — evershop 9.8AICriticalAI2026-02-10
CVE-2026-25947 Worklenz Boolean-Based Blind SQL Injection via Improper ORDER BY Clause Input Validation — worklenz 8.8 High2026-02-10
CVE-2026-1602 Ivanti Endpoint Manager SQL注入漏洞 — Endpoint Manager 6.5 Medium2026-02-10
CVE-2025-7636 SQLi in Ergosis Security Systems' ZEUS PDKS — ZEUS PDKS 8.8 High2026-02-10
CVE-2026-2094 Flowring|Docpedia - SQL Injection — Docpedia 8.8 High2026-02-10
CVE-2026-2093 Flowring|Docpedia - SQL Injection — Docpedia 7.5 High2026-02-10
CVE-2026-25495 Craft has a SQL Injection in Element Indexes via criteria[orderBy] — cms 8.8AIHighAI2026-02-09
CVE-2025-6830 SQLi in Xpoda Türkiye Information Technology's Password Module — Password Module 9.8 Critical2026-02-09

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