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-4485 itsourcecode Gym Management System ajax.php sql injection — Gym Management System 7.3 High 2025-05-09
CVE-2025-4484 itsourcecode Gym Management System ajax.php sql injection — Gym Management System 7.3 High 2025-05-09
CVE-2025-4483 itsourcecode Gym Management System view_pdetails.php sql injection — Gym Management System 7.3 High 2025-05-09
CVE-2025-4482 Project Worlds Student Project Allocation System forgot_password_sql.php sql injection — Student Project Allocation System 7.3 High 2025-05-09
CVE-2025-4481 SourceCodester Apartment Visitor Management System search-result.php sql injection — Apartment Visitor Management System 7.3 High 2025-05-09
CVE-2025-4467 SourceCodester Online Student Clearance System edit-admin.php sql injection — Online Student Clearance System 7.3 High 2025-05-09
CVE-2025-4466 itsourcecode Gym Management System ajax.php sql injection — Gym Management System 7.3 High 2025-05-09
CVE-2025-4465 itsourcecode Gym Management System ajax.php sql injection — Gym Management System 7.3 High 2025-05-09
CVE-2025-4464 itsourcecode Gym Management System ajax.php sql injection — Gym Management System 7.3 High 2025-05-09
CVE-2025-4463 itsourcecode Gym Management System ajax.php sql injection — Gym Management System 7.3 High 2025-05-09
CVE-2025-4459 code-projects Patient Record Management System fecalysis_form.php sql injection — Patient Record Management System 6.3 Medium 2025-05-09
CVE-2025-4458 code-projects Patient Record Management System edit_upatient.php sql injection — Patient Record Management System 6.3 Medium 2025-05-09
CVE-2025-4457 Project Worlds Car Rental Project approve.php sql injection — Car Rental Project 7.3 High 2025-05-09
CVE-2025-4456 Project Worlds Car Rental Project signup.php sql injection — Car Rental Project 7.3 High 2025-05-09
CVE-2025-46828 Unauthenticated SQL Injection on get_socios.php endpoint — WeGIA 9.8AI Critical AI 2025-05-07
CVE-2025-47657 WordPress Productive Commerce plugin <= 1.1.40 - SQL Injection vulnerability — Productive Commerce 9.3 Critical 2025-05-07
CVE-2025-47643 WordPress ELEX Product Feed for WooCommerce <= 3.1.2 - SQL Injection Vulnerability — ELEX Product Feed for WooCommerce 7.6 High 2025-05-07
CVE-2025-47587 WordPress YaySMTP plugin <= 2.6.4 - SQL Injection Vulnerability — YaySMTP 7.6 High 2025-05-07
CVE-2025-47544 WordPress Dynamic Pricing With Discount Rules for WooCommerce plugin <= 4.5.8 - SQL Injection Vulnerability — Dynamic Pricing With Discount Rules for WooCommerce 7.6 High 2025-05-07
CVE-2025-47538 WordPress Cart tracking for WooCommerce plugin <= 1.0.17 - SQL Injection Vulnerability — Cart tracking for WooCommerce 7.6 High 2025-05-07
CVE-2025-47537 WordPress PDF Invoice Builder for WooCommerce plugin <= 5.3.8 - SQL Injection Vulnerability — PDF Invoice Builder for WooCommerce 7.6 High 2025-05-07
CVE-2025-47490 WordPress Ultimate WP Mail plugin <= 1.3.4 - SQL Injection Vulnerability — Ultimate WP Mail 8.5 High 2025-05-07
CVE-2025-47460 WordPress TrackShip for WooCommerce plugin <= 1.9.1 - SQL Injection Vulnerability — TrackShip for WooCommerce 7.6 High 2025-05-07
CVE-2025-0668 BOINC Server Multiple SQL Injections — BOINC Server 5.4AI Medium AI 2025-05-07
CVE-2025-0853 PGS Core <= 5.8.0 - Unauthenticated SQL Injection — PGS Core 7.5 High 2025-05-06
CVE-2025-4363 itsourcecode Gym Management System ajax.php sql injection — Gym Management System 7.3 High 2025-05-06
CVE-2025-4362 itsourcecode Gym Management System ajax.php sql injection — Gym Management System 7.3 High 2025-05-06
CVE-2025-4361 PHPGurukul Company Visitor Management System department.php sql injection — Company Visitor Management System 7.3 High 2025-05-06
CVE-2025-4360 itsourcecode Gym Management System view_member.php sql injection — Gym Management System 7.3 High 2025-05-06
CVE-2025-4359 itsourcecode Gym Management System ajax.php sql injection — Gym Management System 7.3 High 2025-05-06

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