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

Goal: 1000 CNY · Raised: 1336 CNY

100%

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

9771 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-2024-12706 SQL Injection vulnerability discovered in OpenText™ Digital Asset Management. — Digital Asset Management. 8.8AIHighAI2025-04-28
CVE-2025-4030 PHPGurukul COVID19 Testing Management System search-report-result.php sql injection — COVID19 Testing Management System 7.3 High2025-04-28
CVE-2025-4028 PHPGurukul COVID19 Testing Management System profile.php sql injection — COVID19 Testing Management System 7.3 High2025-04-28
CVE-2025-4027 PHPGurukul Old Age Home Management System rules.php sql injection — Old Age Home Management System 7.3 High2025-04-28
CVE-2025-4026 PHPGurukul Nipah Virus Testing Management System profile.php sql injection — Nipah Virus Testing Management System 7.3 High2025-04-28
CVE-2025-4025 itsourcecode Placement Management System registration.php sql injection — Placement Management System 7.3 High2025-04-28
CVE-2025-4024 itsourcecode Placement Management System add_drive.php sql injection — Placement Management System 7.3 High2025-04-28
CVE-2025-4023 itsourcecode Placement Management System add_company.php sql injection — Placement Management System 7.3 High2025-04-28
CVE-2025-4021 code-projects Patient Record Management System edit_spatient.php sql injection — Patient Record Management System 6.3 Medium2025-04-28
CVE-2025-4020 PHPGurukul Old Age Home Management System contact.php sql injection — Old Age Home Management System 7.3 High2025-04-28
CVE-2025-4014 PHPGurukul Art Gallery Management System manage-art-medium.php sql injection — Art Gallery Management System 7.3 High2025-04-28
CVE-2025-4013 PHPGurukul Art Gallery Management System aboutus.php sql injection — Art Gallery Management System 7.3 High2025-04-28
CVE-2025-4005 PHPGurukul COVID19 Testing Management System patient-report.php sql injection — COVID19 Testing Management System 7.3 High2025-04-28
CVE-2025-4004 PHPGurukul COVID19 Testing Management System password-recovery.php sql injection — COVID19 Testing Management System 7.3 High2025-04-28
CVE-2025-3998 CodeAstro Membership Management System renew.php sql injection — Membership Management System 7.3 High2025-04-28
CVE-2025-3976 PHPGurukul COVID19 Testing Management System new-user-testing.php sql injection — COVID19 Testing Management System 7.3 High2025-04-27
CVE-2025-3974 PHPGurukul COVID19 Testing Management System edit-phlebotomist.php sql injection — COVID19 Testing Management System 7.3 High2025-04-27
CVE-2025-3973 PHPGurukul COVID19 Testing Management System check_availability.php sql injection — COVID19 Testing Management System 7.3 High2025-04-27
CVE-2025-3972 PHPGurukul COVID19 Testing Management System bwdates-report-result.php sql injection — COVID19 Testing Management System 7.3 High2025-04-27
CVE-2025-3971 PHPGurukul COVID19 Testing Management System add-phlebotomist.php sql injection — COVID19 Testing Management System 7.3 High2025-04-27
CVE-2025-3968 codeprojects News Publishing Site Dashboard api.php sql injection — News Publishing Site Dashboard 6.3 Medium2025-04-27
CVE-2025-3957 opplus springboot-admin SysLogDao.xml sql injection — springboot-admin 6.3 Medium2025-04-27
CVE-2025-3956 201206030 novel-cloud BookInfoMapper.xml RestResp sql injection — novel-cloud 6.3 Medium2025-04-27
CVE-2025-46578 ZTE GoldenDB Database product has SQL injection vulnerabilities in multiple interfaces — GoldenDB 6.5 Medium2025-04-27
CVE-2025-46577 ZTE GoldenDB Database product has an SQL injection vulnerability — GoldenDB 6.5 Medium2025-04-27
CVE-2025-3955 codeprojects Patient Record Management System edit_rpatient.php.php sql injection — Patient Record Management System 6.3 Medium2025-04-27
CVE-2025-46546 Sherpa Orchestrator SQL注入漏洞 — Orchestrator 3.5 Low2025-04-25
CVE-2025-39377 WordPress Appsero Helper plugin <= 1.3.4 - SQL Injection vulnerability — Appsero Helper 8.5 High2025-04-24
CVE-2025-46248 WordPress Frontend Dashboard plugin <= 2.2.5 - SQL Injection Vulnerability — Frontend Dashboard 9.3 Critical2025-04-24
CVE-2025-3872 Privilege escalation by altering payload in contact form — Centreon 7.2 High2025-04-24

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