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

Goal: 1000 CNY · Raised: 1336 CNY

100%

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

10280 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-3333 codeprojects Online Restaurant Management System menu_update.php sql injection — Online Restaurant Management System 7.3 High 2025-04-07
CVE-2025-3332 codeprojects Online Restaurant Management System menu_save.php sql injection — Online Restaurant Management System 7.3 High 2025-04-07
CVE-2025-3331 codeprojects Online Restaurant Management System payment_save.php sql injection — Online Restaurant Management System 7.3 High 2025-04-07
CVE-2025-3330 codeprojects Online Restaurant Management System reservation_save.php sql injection — Online Restaurant Management System 7.3 High 2025-04-07
CVE-2025-3323 godcheese/code-projects Nimrod ViewMenuCategoryRestController.java searchAllByName sql injection — Nimrod 6.3 Medium 2025-04-06
CVE-2025-3318 Kenj_Frog 肯尼基蛙 company-financial-management 公司财务管理系统 ShangpinleixingController.java page sql injection — company-financial-management 公司财务管理系统 6.3 Medium 2025-04-06
CVE-2025-3316 PHPGurukul Men Salon Management System search-invoices.php sql injection — Men Salon Management System 7.3 High 2025-04-06
CVE-2025-3315 SourceCodester Apartment Visitor Management System view-report.php sql injection — Apartment Visitor Management System 7.3 High 2025-04-06
CVE-2025-3314 SourceCodester Apartment Visitor Management System forgotpw.php sql injection — Apartment Visitor Management System 7.3 High 2025-04-06
CVE-2025-3313 PHPGurukul Men Salon Management System add-customer.php sql injection — Men Salon Management System 7.3 High 2025-04-06
CVE-2025-3312 PHPGurukul Men Salon Management System add-customer-services.php sql injection — Men Salon Management System 7.3 High 2025-04-06
CVE-2025-3311 PHPGurukul Men Salon Management System about-us.php sql injection — Men Salon Management System 7.3 High 2025-04-06
CVE-2025-3310 code-projects Blood Bank Management System delete.php sql injection — Blood Bank Management System 7.3 High 2025-04-06
CVE-2025-3309 code-projects Blood Bank Management System campsdetails.php sql injection — Blood Bank Management System 7.3 High 2025-04-06
CVE-2025-1264 Broken Link Checker by AIOSEO <= 1.2.3 - Authenticated (Contributor+) SQL Injection — Broken Link Checker by AIOSEO – Easily Fix/Monitor Internal and External links 6.5 Medium 2025-04-06
CVE-2025-3308 code-projects Blood Bank Management System viewrequest.php sql injection — Blood Bank Management System 7.3 High 2025-04-06
CVE-2025-3307 code-projects Blood Bank Management System reset.php sql injection — Blood Bank Management System 7.3 High 2025-04-06
CVE-2025-3306 code-projects Blood Bank Management System don.php sql injection — Blood Bank Management System 7.3 High 2025-04-06
CVE-2025-3304 code-projects Patient Record Management System dental_not.php sql injection — Patient Record Management System 6.3 Medium 2025-04-05
CVE-2025-3303 code-projects Patient Record Management System birthing_record.php sql injection — Patient Record Management System 6.3 Medium 2025-04-05
CVE-2025-3299 PHPGurukul Men Salon Management System appointment.php sql injection — Men Salon Management System 7.3 High 2025-04-05
CVE-2025-3296 SourceCodester Online Eyewear Shop Users.php sql injection — Online Eyewear Shop 6.3 Medium 2025-04-05
CVE-2025-3267 qinguoyi TinyWebServer http_conn.cpp sql injection — TinyWebServer 6.3 Medium 2025-04-04
CVE-2025-3265 PHPGurukul e-Diary Management System add-category.php sql injection — e-Diary Management System 7.3 High 2025-04-04
CVE-2025-3258 PHPGurukul Old Age Home Management System search.php sql injection — Old Age Home Management System 7.3 High 2025-04-04
CVE-2025-32203 WordPress Falling things Plugin <= 1.08 - SQL Injection vulnerability — Falling things 7.6 High 2025-04-04
CVE-2025-32204 WordPress Split Test For Elementor Plugin <= 1.8.3 - SQL Injection vulnerability — Split Test For Elementor 7.6 High 2025-04-04
CVE-2025-32148 WordPress Daisycon prijsvergelijkers plugin <= 4.8.4 - SQL Injection vulnerability — Daisycon prijsvergelijkers 8.5 High 2025-04-04
CVE-2025-32149 WordPress teachPress plugin <= 9.0.11 - SQL Injection vulnerability — teachPress 8.5 High 2025-04-04
CVE-2025-32127 WordPress onOffice for WP-Websites plugin <= 5.7 - SQL Injection vulnerability — onOffice for WP-Websites 7.6 High 2025-04-04

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