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-2025-4263 PHPGurukul Online DJ Booking Management System booking-search.php sql injection — Online DJ Booking Management System 7.3 High2025-05-05
CVE-2025-4262 PHPGurukul Online DJ Booking Management System user-search.php sql injection — Online DJ Booking Management System 7.3 High2025-05-05
CVE-2025-4250 code-projects Nero Social Networking Site index.php sql injection — Nero Social Networking Site 7.3 High2025-05-04
CVE-2025-4249 PHPGurukul e-Diary Management System manage-categories.php sql injection — e-Diary Management System 7.3 High2025-05-04
CVE-2025-4248 SourceCodester Simple To-Do List System complete_task.php sql injection — Simple To-Do List System 6.3 Medium2025-05-04
CVE-2025-4247 SourceCodester Simple To-Do List System delete_task.php sql injection — Simple To-Do List System 6.3 Medium2025-05-04
CVE-2025-4244 code-projects Online Bus Reservation System seatlocation.php sql injection — Online Bus Reservation System 6.3 Medium2025-05-03
CVE-2025-4243 code-projects Online Bus Reservation System print.php sql injection — Online Bus Reservation System 6.3 Medium2025-05-03
CVE-2025-4242 PHPGurukul Online Birth Certificate System between-dates-report.php sql injection — Online Birth Certificate System 7.3 High2025-05-03
CVE-2025-4241 PHPGurukul Teacher Subject Allocation Management System search.php sql injection — Teacher Subject Allocation Management System 7.3 High2025-05-03
CVE-2025-4226 PHPGurukul/Campcodes Cyber Cafe Management System add-computer.php sql injection — Cyber Cafe Management System 7.3 High2025-05-03
CVE-2025-4214 PHPGuruku Online DJ Booking Management System booking-bwdates-reports-details.php sql injection — Online DJ Booking Management System 7.3 High2025-05-02
CVE-2025-4213 PHPGurukul Online Birth Certificate System search.php sql injection — Online Birth Certificate System 7.3 High2025-05-02
CVE-2025-4204 Ultimate Auction Pro <= 1.5.2 - Unauthenticated SQL Injection via 'auction_id' — Ultimate Auction Pro 7.5 High2025-05-02
CVE-2025-2812 SQLi in Mydata Informatics' Ticket Sales Automation — Ticket Sales Automation 9.8 Critical2025-05-02
CVE-2024-12023 FULL – Cliente 3.1.5 - 3.1.25 - Authenticated (Subscriber+) SQL Injection — FULL – Cliente 6.5 Medium2025-05-02
CVE-2024-13322 Ads Pro Plugin - Multi-Purpose WordPress Advertising Manager <= 4.88 - Unauthenticated SQL Injection — Ads Pro Plugin - Multi-Purpose WordPress Advertising Manager 7.5 High2025-05-02
CVE-2024-13344 Advance Seat Reservation Management for WooCommerce <= 3.3 - Unauthenticated SQL Injection — Advance Seat Reservation Management for WooCommerce 7.5 High2025-05-02
CVE-2025-3708 Le-show Medical Practice Management System - SQL Injection — Le-show 9.8 Critical2025-05-02
CVE-2025-3707 Sunnet eHRD CTMS - SQL Injection — eHRD CTMS 6.5 Medium2025-05-02
CVE-2025-4197 code-projects Patient Record Management System edit_xpatient.php sql injection — Patient Record Management System 6.3 Medium2025-05-02
CVE-2025-4196 SourceCodester Patient Record Management System birthing.php sql injection — Patient Record Management System 6.3 Medium2025-05-02
CVE-2025-4195 itsourcecode Gym Management System ajax.php sql injection — Gym Management System 7.3 High2025-05-02
CVE-2025-4193 itsourcecode Restaurant Management System category_update.php sql injection — Restaurant Management System 7.3 High2025-05-02
CVE-2025-4192 itsourcecode Restaurant Management System category_save.php sql injection — Restaurant Management System 7.3 High2025-05-02
CVE-2025-4191 PHPGurukul Employee Record Management System editmyeducation.php sql injection — Employee Record Management System 7.3 High2025-05-02
CVE-2025-4176 PHPGurukul Blood Bank & Donor Management System request-received-bydonar.php sql injection — Blood Bank & Donor Management System 7.3 High2025-05-01
CVE-2025-4174 PHPGurukul COVID19 Testing Management System login.php sql injection — COVID19 Testing Management System 7.3 High2025-05-01
CVE-2025-46337 SQL injection in ADOdb PostgreSQL driver pg_insert_id() method — ADOdb 10.0 Critical2025-05-01
CVE-2025-4173 SourceCodester Online Eyewear Shop Master.php delete_cart sql injection — Online Eyewear Shop 6.3 Medium2025-05-01

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