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-32466 Extension - rsjoomla.com - SQL injection vulnerability in RSMediaGallery! component 1.7.4 - 2.1.7 for Joomla — RSMediaGallery component for Joomla 7.6AI High AI 2025-06-11
CVE-2025-5980 code-projects Restaurant Order System order.php sql injection — Restaurant Order System 7.3 High 2025-06-10
CVE-2025-5979 code-projects School Fees Payment System branch.php sql injection — School Fees Payment System 7.3 High 2025-06-10
CVE-2025-5977 code-projects School Fees Payment System datatable.php sql injection — School Fees Payment System 7.3 High 2025-06-10
CVE-2025-5971 code-projects School Fees Payment System ajx.php sql injection — School Fees Payment System 6.3 Medium 2025-06-10
CVE-2025-47172 Microsoft SharePoint Server Remote Code Execution Vulnerability — Microsoft SharePoint Enterprise Server 2016 8.8 High 2025-06-10
CVE-2025-49455 WordPress WordPress-WPJobBoard <= 25.07010000-WP6.8.1-JB5.11.5 - SQL Injection Vulnerability — WordPress-WPJobBoard 9.3 Critical 2025-06-10
CVE-2025-40657 SQL injection vulnerability in DM Corporative CMS — DM Corporative CMS 9.8AI Critical AI 2025-06-10
CVE-2025-40656 SQL injection vulnerability in DM Corporative CMS — DM Corporative CMS 9.8AI Critical AI 2025-06-10
CVE-2025-40655 SQL injection vulnerability in DM Corporative CMS — DM Corporative CMS 9.8AI Critical AI 2025-06-10
CVE-2025-40654 SQL injection vulnerability in DM Corporative CMS — DM Corporative CMS 9.8AI Critical AI 2025-06-10
CVE-2025-5913 PHPGurukul Vehicle Record Management System search-vehicle.php sql injection — Vehicle Record Management System 7.3 High 2025-06-10
CVE-2025-30507 CyberData 011209 SIP Emergency Intercom SQL Injection — 011209 SIP Emergency Intercom 5.3 Medium 2025-06-09
CVE-2025-24767 WordPress TicketBAI Facturas para WooCommerce plugin <= 3.19 - SQL Injection Vulnerability — TicketBAI Facturas para WooCommerce 9.3 Critical 2025-06-09
CVE-2025-31059 WordPress WBW Product Table PRO plugin <= 2.2.6 - SQL Injection vulnerability — WBW Product Table PRO 9.3 Critical 2025-06-09
CVE-2025-31424 WordPress WP Lead Capturing Pages plugin < 2.6 - SQL Injection vulnerability — WP Lead Capturing Pages 9.3 Critical 2025-06-09
CVE-2025-31920 WordPress WP Guppy plugin <= 4.3.3 - SQL Injection Vulnerability — WP Guppy 8.5 High 2025-06-09
CVE-2025-47608 WordPress Recover abandoned cart for WooCommerce plugin <= 2.5 - SQL Injection Vulnerability — Recover abandoned cart for WooCommerce 9.3 Critical 2025-06-09
CVE-2025-47651 WordPress Infility Global plugin <= 2.15.06 - SQL Injection vulnerability — Infility Global 8.5 High 2025-06-09
CVE-2025-48122 WordPress Spreadsheet Price Changer for WooCommerce and WP E-commerce – Light plugin <= 2.4.37 - SQL Injection Vulnerability — Spreadsheet Price Changer for WooCommerce and WP E-commerce – Light 9.3 Critical 2025-06-09
CVE-2025-48141 WordPress Multi CryptoCurrency Payments plugin <= 2.0.7 - SQL Injection Vulnerability — Multi CryptoCurrency Payments 9.3 Critical 2025-06-09
CVE-2025-48281 WordPress MyStyle Custom Product Designer plugin <= 3.21.1 - SQL Injection Vulnerability — MyStyle Custom Product Designer 9.3 Critical 2025-06-09
CVE-2025-5881 code-projects Chat System confirm_password.php sql injection — Chat System 6.3 Medium 2025-06-09
CVE-2025-41444 SQL Injection — ADAudit Plus 8.3 High 2025-06-09
CVE-2025-36528 SQL Injection — ADAudit Plus 8.3 High 2025-06-09
CVE-2025-27709 SQL Injection — ADAudit Plus 8.3 High 2025-06-09
CVE-2025-5860 PHPGurukul Maid Hiring Management System search-booking-request.php sql injection — Maid Hiring Management System 7.3 High 2025-06-09
CVE-2025-5859 PHPGurukul Nipah Virus Testing Management System test-details.php sql injection — Nipah Virus Testing Management System 6.3 Medium 2025-06-09
CVE-2025-5858 PHPGurukul Nipah Virus Testing Management System patient-report.php sql injection — Nipah Virus Testing Management System 6.3 Medium 2025-06-09
CVE-2025-5857 code-projects Patient Record Management System urinalysis_record.php sql injection — Patient Record Management System 6.3 Medium 2025-06-09

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