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

Goal: 1000 CNY · Raised: 1336 CNY

100%

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

9921 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-2025-27617 Pimcore Vulnerable to SQL Injection in getRelationFilterCondition — pimcore 8.8 -2025-03-11
CVE-2024-33501 Fortinet FortiManager和Fortinet FortiAnalyzer SQL注入漏洞 — FortiManager 4.0 Medium2025-03-11
CVE-2024-54026 Fortinet FortiSandbox SQL注入漏洞 — FortiSandbox 4.1 Medium2025-03-11
CVE-2025-22370 Mennekes smart/premium charges systems, SQL Injection in web configuration interface — Smart / Premium charging stations 8.8 -2025-03-11
CVE-2025-2132 ftcms Search ajax_all_lists sql injection — ftcms 4.7 Medium2025-03-09
CVE-2025-2126 JoomlaUX JUX Real Estate GET Parameter realties sql injection — JUX Real Estate 6.3 Medium2025-03-09
CVE-2025-2118 Quantico Tecnologia PRMV Login Endpoint login.php sql injection — PRMV 7.3 High2025-03-09
CVE-2025-2117 Beijing Founder Electronics Founder Enjoys All-Media Acquisition and Editing System reportCenter.do electricDocList sql injection — Founder Enjoys All-Media Acquisition and Editing System 6.3 Medium2025-03-09
CVE-2025-2113 AT Software Solutions ATSVD Esqueceu a senha sql injection — ATSVD 7.3 High2025-03-09
CVE-2025-2112 user-xiangpeng yaoqishan MediaInfoService.java getMediaLisByFilter sql injection — yaoqishan 6.3 Medium2025-03-08
CVE-2025-1323 WP-Recall – Registration, Profile, Commerce & More <= 16.26.10 - Unauthenticated SQL Injection — WP-Recall – Registration, Profile, Commerce & More 7.5 High2025-03-08
CVE-2024-13844 Post SMTP <= 3.1.2 - Authenticated (Administrator+) SQL Injection via columns Parameter — Post SMTP – Complete Email Deliverability and SMTP Solution with Email Logs, Alerts, Backup SMTP & Mobile App 4.9 Medium2025-03-08
CVE-2025-2088 PHPGurukul Pre-School Enrollment System profile.php sql injection — Pre-School Enrollment System 7.3 High2025-03-07
CVE-2025-1768 SEO Plugin by Squirrly SEO <= 12.4.05 - Authenticated (Subscriber+) SQL Injection via search Parameter — SEO Plugin by Squirrly SEO 6.5 Medium2025-03-07
CVE-2024-12609 School Management System for Wordpress <= 92.0.0 - Authenticated (Student+) SQL Injection via 'view-attendance' — School Management System for Wordpress 6.5 Medium2025-03-07
CVE-2024-13781 Hero Maps Premium - Customizable Google Maps Plugin <= 2.3.9 - Authenticated (Subscriber+) SQL Injection — Hero Maps Premium 6.5 Medium2025-03-07
CVE-2024-12607 School Management System for Wordpress <= 92.0.0 - Authenticated (Subscriber+) SQL Injection via 'mj_smgt_show_event_task' — School Management System for Wordpress 6.5 Medium2025-03-07
CVE-2024-13320 CURCY - WooCommerce Multi Currency - Currency Switcher <= 2.3.6 - Unauthenticated SQL Injection — CURCY - WooCommerce Multi Currency - Currency Switcher 7.5 High2025-03-07
CVE-2025-2067 projectworlds Life Insurance Management System search.php sql injection — Life Insurance Management System 7.3 High2025-03-07
CVE-2025-2066 projectworlds Life Insurance Management System updateAgent.php sql injection — Life Insurance Management System 7.3 High2025-03-07
CVE-2025-2065 projectworlds Life Insurance Management System editAgent.php sql injection — Life Insurance Management System 7.3 High2025-03-07
CVE-2025-2064 projectworlds Life Insurance Management System deletePayment.php sql injection — Life Insurance Management System 7.3 High2025-03-07
CVE-2025-2063 projectworlds Life Insurance Management System deleteNominee.php sql injection — Life Insurance Management System 7.3 High2025-03-07
CVE-2025-2062 projectworlds Life Insurance Management System clientStatus.php sql injection — Life Insurance Management System 7.3 High2025-03-07
CVE-2025-2060 PHPGurukul Emergency Ambulance Hiring Portal admin-profile.php sql injection — Emergency Ambulance Hiring Portal 7.3 High2025-03-07
CVE-2025-2059 PHPGurukul Emergency Ambulance Hiring Portal booking-details.php sql injection — Emergency Ambulance Hiring Portal 7.3 High2025-03-07
CVE-2025-2058 PHPGurukul Emergency Ambulance Hiring Portal search.php sql injection — Emergency Ambulance Hiring Portal 7.3 High2025-03-07
CVE-2025-2057 PHPGurukul Emergency Ambulance Hiring Portal about-us.php sql injection — Emergency Ambulance Hiring Portal 7.3 High2025-03-07
CVE-2025-2054 code-projects Blood Bank Management System edit_state.php sql injection — Blood Bank Management System 4.7 Medium2025-03-07
CVE-2025-2053 PHPGurukul Apartment Visitors Management System visitor-detail.php sql injection — Apartment Visitors Management System 6.3 Medium2025-03-07

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