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

Goal: 1000 CNY · Raised: 1336 CNY

100%

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

10283 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, Availability Execute 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.
Confidentiality Read Application Data
Since SQL databases generally hold sensitive data, loss of confidentiality is a frequent problem with SQL injection vulnerabilities.
Authentication Gain 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 Control Bypass 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.
Integrity Modify 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 Design Use 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 Design If 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, Operation Run 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 Design For 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.
Implementation While 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 ID Title CVSS Severity Published
CVE-2025-8158 PHPGurukul Login and User Management System yesterday-reg-users.php sql injection — Login and User Management System 6.3 Medium 2025-07-25
CVE-2025-8157 PHPGurukul User Registration & Login and User Management lastthirtyays-reg-users.php sql injection — User Registration & Login and User Management 6.3 Medium 2025-07-25
CVE-2025-8156 PHPGurukul User Registration & Login and User Management lastsevendays-reg-users.php sql injection — User Registration & Login and User Management 6.3 Medium 2025-07-25
CVE-2025-8135 itsourcecode Insurance Management System updateAgent.php sql injection — Insurance Management System 6.3 Medium 2025-07-25
CVE-2025-8134 PHPGurukul BP Monitoring Management System bwdates-report-result.php sql injection — BP Monitoring Management System 6.3 Medium 2025-07-25
CVE-2025-8127 deerwms deer-wms-2 list sql injection — deer-wms-2 6.3 Medium 2025-07-25
CVE-2025-8126 deerwms deer-wms-2 export sql injection — deer-wms-2 6.3 Medium 2025-07-25
CVE-2025-8125 deerwms deer-wms-2 allocatedList sql injection — deer-wms-2 6.3 Medium 2025-07-25
CVE-2025-8124 deerwms deer-wms-2 unallocatedList sql injection — deer-wms-2 6.3 Medium 2025-07-24
CVE-2025-54379 eKuiper API endpoints handling SQL queries with user-controlled table names. — ekuiper 9.8 - 2025-07-24
CVE-2025-32429 XWiki Platform vulnerable to SQL injection through getdeleteddocuments.vm template sort parameter — xwiki-platform 9.8 - 2025-07-24
CVE-2025-8123 deerwms deer-wms-2 edit sql injection — deer-wms-2 6.3 Medium 2025-07-24
CVE-2025-4784 SQLi in Moderec's Tourtella — Tourtella 9.8 Critical 2025-07-24
CVE-2025-4822 SQLi in Bayraktar Solar Energies' ScadaWatt Otopilot — ScadaWatt Otopilot 9.8 Critical 2025-07-24
CVE-2025-54294 Extension - stackideas.com - SQLi vulnerability in Komento component 4.0.0-4.0.7 for Joomla — Komento component for Joomla 9.8 - 2025-07-23
CVE-2025-50127 Extension - dj-extensions.com - SQLi vulnerability in DJ-Flyer component 1.0-3.2 for Joomla — DJ-Flyer component for Joomla 7.2 - 2025-07-23
CVE-2025-43022 Poly Clariti Manager - Multiple Security Vulnerabilities — Poly Clariti Manager 7.2 - 2025-07-22
CVE-2025-8018 code-projects Food Ordering Review System reservation_page.php sql injection — Food Ordering Review System 6.3 Medium 2025-07-22
CVE-2025-4285 SQLi in Rolantis Information Technologies' Agentis — Agentis 10.0 Critical 2025-07-22
CVE-2025-7950 code-projects Public Chat Room login.php sql injection — Public Chat Room 7.3 High 2025-07-22
CVE-2025-7936 fuyang_lipengjun platform ScheduleJobLogController.java queryPage sql injection — platform 6.3 Medium 2025-07-21
CVE-2025-7935 fuyang_lipengjun platform SysLogController.java SysLogController sql injection — platform 6.3 Medium 2025-07-21
CVE-2025-7934 fuyang_lipengjun platform ScheduleJobController.java queryPage sql injection — platform 6.3 Medium 2025-07-21
CVE-2025-7933 Campcodes Sales and Inventory System Setting settings_update.php sql injection — Sales and Inventory System 7.3 High 2025-07-21
CVE-2025-7930 code-projects Church Donation System add_members.php sql injection — Church Donation System 7.3 High 2025-07-21
CVE-2025-7929 code-projects Church Donation System edit_Members.php sql injection — Church Donation System 7.3 High 2025-07-21
CVE-2025-7928 code-projects Church Donation System edit_user.php sql injection — Church Donation System 7.3 High 2025-07-21
CVE-2025-7927 PHPGurukul Online Banquet Booking System view-user-queries.php sql injection — Online Banquet Booking System 6.3 Medium 2025-07-21
CVE-2024-13973 Sophos Firewall 安全漏洞 — Sophos Firewall 6.8 Medium 2025-07-21
CVE-2025-7624 Sophos Firewall 安全漏洞 — Sophos Firewall 9.8 Critical 2025-07-21

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