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

Goal: 1000 CNY · Raised: 1325 CNY

100%

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

9438 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-10396 SourceCodester Pet Grooming Management Software edit_role.php sql injection — Pet Grooming Management Software 7.3 High2025-09-14
CVE-2025-10387 codesiddhant Jasmin Ransomware handshake.php sql injection — Jasmin Ransomware 6.3 Medium2025-09-14
CVE-2025-27240 Secondary-order SQL injection in Zabbix Server when deleting an autoregistered host — Zabbix 7.2 -2025-09-12
CVE-2025-10266 NewType Infortech|NUP Portal - SQL Injection — NUP Portal 9.8 Critical2025-09-12
CVE-2025-9807 The Events Calendar <= 6.15.1 - Unauthenticated SQL Injection — The Events Calendar 7.5 High2025-09-12
CVE-2025-10251 FoxCMS Images.php batchCope sql injection — FoxCMS 6.3 Medium2025-09-11
CVE-2025-40692 SQL injection in PHPGurukul Online Fire Reporting System — Online Fire Reporting System 9.8AICriticalAI2025-09-11
CVE-2025-40691 SQL injection in PHPGurukul Online Fire Reporting System — Online Fire Reporting System 9.8AICriticalAI2025-09-11
CVE-2025-40690 SQL injection in PHPGurukul Online Fire Reporting System — Online Fire Reporting System 9.8AICriticalAI2025-09-11
CVE-2025-40689 SQL injection in PHPGurukul Online Fire Reporting System — Online Fire Reporting System 9.8AICriticalAI2025-09-11
CVE-2025-40687 SQL injection in PHPGurukul Online Fire Reporting System — Online Fire Reporting System 9.8AICriticalAI2025-09-11
CVE-2025-9451 Smartcat Translator for WPML <= 3.1.72 - Authenticated (Author+) SQL Injection via orderby Parameter — Smartcat Translator for WPML 6.5 Medium2025-09-11
CVE-2025-8692 Coupon API <= 6.2.12 - Authenticated (Administrator+) SQL Injection via 'log_duration' — Coupon API 4.9 Medium2025-09-11
CVE-2025-9073 All in one Minifier <= 3.2 - Unauthenticated SQL Injection — All in one Minifier 7.5 High2025-09-11
CVE-2025-9776 CatFolders – Tame Your WordPress Media Library by Category <= 2.5.2 - Authenticated (Author+) SQL Injection via CSV Import — CatFolders – WordPress Media Library Folders & Categories 6.5 Medium2025-09-11
CVE-2025-10218 lostvip-com ruoyi-go Background Management SysRoleDao.go SelectListPage sql injection — ruoyi-go 6.3 Medium2025-09-10
CVE-2025-10210 yanyutao0402 ChanCMS Api.js search sql injection — ChanCMS 6.3 Medium2025-09-10
CVE-2025-9943 Unauthenticated SQL Injection Vulnerability in Shibboleth Service Provider — Service Provider 9.1AICriticalAI2025-09-10
CVE-2025-10142 PagBank / PagSeguro Connect para WooCommerce <= 4.44.3 - Authenticated (Shop Manager+) SQL Injection — PagBank / PagSeguro Connect para WooCommerce 4.9 Medium2025-09-10
CVE-2025-7826 Testimonial <= 2.3 - Authenticated (Contributor+) SQL Injection — Testimonial 6.5 Medium2025-09-10
CVE-2025-6189 Duplicate Page and Post <= 2.9.5 - Authenticated (Contributor+) SQL Injection via meta_key Parameter — Duplicate Page and Post 6.5 Medium2025-09-10
CVE-2025-9463 Payments Plugin and Checkout Plugin for WooCommerce: Stripe, PayPal, Square, Authorize.net <= 1.117.5 - Authenticated (Contributor+) SQL Injection via order_by Parameter — PeachPay — Payments & Express Checkout for WooCommerce (supports Stripe, PayPal, Square, Authorize.net, NMI) 6.5 Medium2025-09-10
CVE-2025-10197 HJSoft HCM Human Resources Management System downlawbase sql injection — HCM Human Resources Management System 6.3 Medium2025-09-10
CVE-2025-58448 rAthena has SQL Injection in PartyBooking component via `WorldName` parameter. — rathena 9.1 Critical2025-09-09
CVE-2025-58462 OPEXUS FOIAXpress PAL SQL injection — FOIAXpress Public Access Link (PAL) 9.8 Critical2025-09-09
CVE-2025-58993 WordPress Tutor LMS Plugin <= 3.7.4 - SQL Injection Vulnerability — Tutor LMS 7.6 High2025-09-09
CVE-2025-47569 WordPress WooCommerce Ultimate Gift Card plugin <= 2.9.6 - SQL Injection vulnerability — WooCommerce Ultimate Gift Card 9.3 Critical2025-09-09
CVE-2025-59008 WordPress ZIP Code Based Content Protection plugin <= 1.0.0 - SQL Injection vulnerability — ZIP Code Based Content Protection 7.6 High2025-09-09
CVE-2025-10095 SQL injection in SMPP component of SMSEagle firmware — SMSEagle 9.8AICriticalAI2025-09-09
CVE-2025-10122 Maccms10 Database.php rep sql injection — Maccms10 4.7 Medium2025-09-09

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