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

Goal: 1000 CNY · Raised: 1336 CNY

100%

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

9614 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-32924 WordPress Revy plugin <= 2.1 - SQL Injection vulnerability — Revy 8.5 High2025-05-19
CVE-2025-39355 WordPress FAT Services Booking plugin <= 5.6 - SQL Injection vulnerability — FAT Services Booking 8.5 High2025-05-19
CVE-2025-39357 WordPress Hospital Management System plugin <= 47.0(20-11-2023) - SQL Injection vulnerability — Hospital Management System 8.5 High2025-05-19
CVE-2025-39386 WordPress Hospital Management System plugin <= 47.0(20-11-2023) - SQL Injection vulnerability — Hospital Management System 9.3 Critical2025-05-19
CVE-2025-39389 WordPress AnalyticsWP <= 2.1.2 - SQL Injection Vulnerability — AnalyticsWP 9.3 Critical2025-05-19
CVE-2025-39395 WordPress WPAMS plugin <= 44.0 (17-08-2023) - SQL Injection vulnerability — WPAMS 9.3 Critical2025-05-19
CVE-2025-39403 WordPress WPAMS plugin <= 44.0 (17-08-2023) - SQL Injection vulnerability — WPAMS 8.5 High2025-05-19
CVE-2025-39445 WordPress Super Store Finder <= 7.2 - SQL Injection Vulnerability — Super Store Finder 9.3 Critical2025-05-19
CVE-2025-43833 WordPress Absolute Links plugin <= 1.1.1 - SQL Injection vulnerability — Absolute Links 7.6 High2025-05-19
CVE-2025-4941 PHPGurukul Credit Card Application Management System index.php sql injection — Credit Card Application Management System 7.3 High2025-05-19
CVE-2025-39370 WordPress iCafe Library plugin <= 1.8.3 - SQL Injection vulnerability — iCafe Library 7.6 High2025-05-19
CVE-2025-4940 1000 Projects Daily College Class Work Report Book admin_info.php sql injection — Daily College Class Work Report Book 7.3 High2025-05-19
CVE-2025-4938 PHPGurukul Employee Record Management System registererms.php sql injection — Employee Record Management System 6.3 Medium2025-05-19
CVE-2025-4937 SourceCodester Apartment Visitor Management System profile.php sql injection — Apartment Visitor Management System 7.3 High2025-05-19
CVE-2025-48280 WordPress AutomatorWP plugin <= 5.2.1.3 - SQL Injection Vulnerability — AutomatorWP 7.6 High2025-05-19
CVE-2025-48278 WordPress RSVPMarker plugin <= 11.5.6 - SQL Injection Vulnerability — RSVPMarker 8.5 High2025-05-19
CVE-2025-4936 projectworlds Online Food Ordering System admin-page.php sql injection — Online Food Ordering System 7.3 High2025-05-19
CVE-2025-4935 SourceCodester Stock Management System changePassword.php sql injection — Stock Management System 7.3 High2025-05-19
CVE-2025-4934 PHPGurukul User Registration & Login and User Management System edit-profile.php sql injection — User Registration & Login and User Management System 7.3 High2025-05-19
CVE-2025-4933 ponaravindb Hospital-Management-System doctor-panel.php sql injection — Hospital-Management-System 6.3 Medium2025-05-19
CVE-2025-4932 projectworlds Online Lawyer Management System lawyer_registation.php sql injection — Online Lawyer Management System 7.3 High2025-05-19
CVE-2025-4931 projectworlds Online Lawyer Management System user_registation.php sql injection — Online Lawyer Management System 7.3 High2025-05-19
CVE-2025-4930 Campcodes Online Shopping Portal my-cart.php sql injection — Online Shopping Portal 7.3 High2025-05-19
CVE-2025-4929 Campcodes Online Shopping Portal my-account.php sql injection — Online Shopping Portal 7.3 High2025-05-19
CVE-2025-4928 projectworlds Online Lawyer Management System save_lawyer_edit_profile.php sql injection — Online Lawyer Management System 7.3 High2025-05-19
CVE-2025-4927 PHPGurukul Online Marriage Registration System between-dates-application-report.php sql injection — Online Marriage Registration System 7.3 High2025-05-19
CVE-2025-4925 PHPGurukul Daily Expense Tracker System expense-monthwise-reports-detailed.php sql injection — Daily Expense Tracker System 7.3 High2025-05-19
CVE-2025-4924 SourceCodester Client Database Management System user_void_transaction.php sql injection — Client Database Management System 7.3 High2025-05-19
CVE-2025-4917 PHPGurukul Auto Taxi Stand Management System new-autoortaxi-entry-form.php sql injection — Auto Taxi Stand Management System 7.3 High2025-05-19
CVE-2025-4916 PHPGurukul Auto Taxi Stand Management System admin-profile.php sql injection — Auto Taxi Stand Management System 7.3 High2025-05-19

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