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

Goal: 1000 CNY · Raised: 1336 CNY

100%

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

10283 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-7765 code-projects Online Appointment Booking System addmanagerclinic.php sql injection — Online Appointment Booking System 7.3 High 2025-07-17
CVE-2025-7764 code-projects Online Appointment Booking System deletedoctorclinic.php sql injection — Online Appointment Booking System 7.3 High 2025-07-17
CVE-2025-7757 PHPGurukul Land Record System edit-property.php sql injection — Land Record System 7.3 High 2025-07-17
CVE-2025-7754 code-projects Patient Record Management System xray_form.php sql injection — Patient Record Management System 6.3 Medium 2025-07-17
CVE-2025-7753 code-projects Online Appointment Booking System adddoctor.php sql injection — Online Appointment Booking System 7.3 High 2025-07-17
CVE-2025-7752 code-projects Online Appointment Booking System deletedoctor.php sql injection — Online Appointment Booking System 7.3 High 2025-07-17
CVE-2025-6230 Lenovo Vantage 安全漏洞 — Vantage 5.3 Medium 2025-07-17
CVE-2025-7751 code-projects Online Appointment Booking System addclinic.php sql injection — Online Appointment Booking System 7.3 High 2025-07-17
CVE-2025-7750 code-projects Online Appointment Booking System adddoctorclinic.php sql injection — Online Appointment Booking System 7.3 High 2025-07-17
CVE-2025-7749 code-projects Online Appointment Booking System getmanagerregion.php sql injection — Online Appointment Booking System 7.3 High 2025-07-17
CVE-2025-25257 Fortinet FortiWeb SQL注入漏洞 — FortiWeb 9.6 Critical 2025-07-17
CVE-2025-54062 WeGIA SQL Injection (Blind Time-Based) Vulnerability in id_dependente Parameter on profile_dependente.php Endpoint — WeGIA 9.8AI Critical AI 2025-07-17
CVE-2025-54061 WeGIASQL Injection (Blind Time-Based) Vulnerability in idatendido_familiares Parameter on dependente_editarDoc.php Endpoint — WeGIA 8.1AI High AI 2025-07-17
CVE-2025-54060 WeGIA SQL Injection (Blind Time-Based) Vulnerability in idatendido_familiares Parameter on dependente_editarInfoPessoal.php Endpoint — WeGIA 8.1AI High AI 2025-07-17
CVE-2025-54058 WeGIA SQL Injection (Blind Time-Based) Vulnerability in idatendido_familiares Parameter on dependente_editarEndereco.php Endpoint — WeGIA 8.1AI High AI 2025-07-17
CVE-2025-53946 WeGIA vulnerable to SQL Injection in endpoint profile_paciente.php parameter id_fichamedica — WeGIA 9.1AI Critical AI 2025-07-17
CVE-2025-7735 UNIMAX|Hospital Information System - SQL Injection — Hospital Information System 7.5 High 2025-07-17
CVE-2025-20272 Cisco Evolved Programmable Network Manager and Cisco Prime Infrastructure Blind SQL Injection Vulnerability — Cisco Evolved Programmable Network Manager (EPNM) 4.3 Medium 2025-07-16
CVE-2025-53937 WeGIA has SQL Injection (Blind Time-Based) Vulnerability in `cargo` Parameter on `control.php` Endpoint — WeGIA 8.8AI High AI 2025-07-16
CVE-2025-24759 WordPress WP-BusinessDirectory <= 3.1.5 - SQL Injection vulnerability — WP-BusinessDirectory 9.3 Critical 2025-07-16
CVE-2025-28959 WordPress URL Shortener <= 3.0.7 - SQL Injection Vulnerability — URL Shortener 9.3 Critical 2025-07-16
CVE-2025-28982 WordPress WP Pipes plugin <= 1.4.3 - SQL Injection Vulnerability — WP Pipes 9.3 Critical 2025-07-16
CVE-2025-30936 WordPress Torod plugin <= 2.1 - SQL Injection vulnerability — Torod 9.3 Critical 2025-07-16
CVE-2025-32574 WordPress WPGYM plugin <= 65.0 - SQL Injection vulnerability — WPGYM 8.5 High 2025-07-16
CVE-2025-47645 WordPress ELEX WooCommerce Advanced Bulk Edit Products, Prices & Attributes plugin <= 1.4.9 - Subscriber+ SQL Injection vulnerability — ELEX WooCommerce Advanced Bulk Edit Products, Prices & Attributes 8.5 High 2025-07-16
CVE-2025-49034 WordPress Funnel Builder by FunnelKit plugin <= 3.10.2 - SQL Injection vulnerability — Funnel Builder by FunnelKit 7.6 High 2025-07-16
CVE-2025-49876 WordPress ProfileGrid plugin <= 5.9.5.2 - SQL Injection vulnerability — ProfileGrid 8.5 High 2025-07-16
CVE-2025-52714 WordPress Traveler theme < 3.2.2 - SQL Injection Vulnerability — Traveler 9.3 Critical 2025-07-16
CVE-2025-52819 WordPress Pakke Envíos plugin <= 1.0.2 - SQL Injection Vulnerability — Pakke Envíos 8.5 High 2025-07-16
CVE-2025-48161 WordPress YaySMTP plugin <= 1.3 - SQL Injection Vulnerability — YaySMTP 7.6 High 2025-07-16

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