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

Goal: 1000 CNY · Raised: 1336 CNY

100%

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

10268 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-23784 WordPress Contact Form 7 Round Robin Lead Distribution Plugin <= 1.2.1 - SQL Injection vulnerability — Contact Form 7 Round Robin Lead Distribution 7.6 High 2025-01-22
CVE-2024-13496 GamiPress <= 7.3.1 - Unauthenticated SQL Injection via orderby Parameter — GamiPress – Gamification plugin to reward points, achievements, badges & ranks in WordPress 7.5 High 2025-01-22
CVE-2024-13426 WP-Polls <= 2.77.2 - Unauthenticated SQL Injection to Stored Cross-Site Scripting — WP-Polls 5.4 Medium 2025-01-22
CVE-2025-22716 WordPress Taskbuilder Plugin <= 3.0.6 - SQL Injection vulnerability — Taskbuilder 8.5 High 2025-01-21
CVE-2025-22710 WordPress Smart Manager Plugin <= 8.52.0 - SQL Injection vulnerability — Smart Manager 7.6 High 2025-01-21
CVE-2025-22553 WordPress Multiple Carousel Plugin <= 2.0 - SQL Injection vulnerability — Multiple Carousel 9.3 Critical 2025-01-21
CVE-2024-51818 WordPress Fancy Product Designer plugin <= 6.4.3 - Unauthenticated SQL Injection vulnerability — Fancy Product Designer 9.3 Critical 2025-01-21
CVE-2024-49666 WordPress ARPrice plugin <= 4.1.3 - SQL Injection vulnerability — ARPrice 8.5 High 2025-01-21
CVE-2024-49333 WordPress Hero Menu plugin <= 1.16.5 - SQL Injection vulnerability — Hero Mega Menu - Responsive WordPress Menu Plugin 8.5 High 2025-01-21
CVE-2024-49303 WordPress Hero Menu plugin <= 1.16.5 - SQL Injection vulnerability — Hero Mega Menu - Responsive WordPress Menu Plugin 8.5 High 2025-01-21
CVE-2024-49655 WordPress ARPrice plugin <= 4.1.3 - Unauthenticated SQL Injection vulnerability — ARPrice 9.3 Critical 2025-01-21
CVE-2024-13230 Social Share, Social Login and Social Comments Plugin – Super Socializer <= 7.14 - Unauthenticated Limited SQL Injection via 'SuperSocializerKey' — Social Share, Social Login and Social Comments Plugin – Super Socializer 5.3 Medium 2025-01-21
CVE-2025-23220 WeGIA has a SQL Injection endpoint 'adicionar_raca.php' parameter 'raca' — WeGIA 9.1 - 2025-01-20
CVE-2025-23219 WeGIA has a SQL Injection endpoint 'adicionar_cor.php' parameter 'cor' — WeGIA 9.1 - 2025-01-20
CVE-2025-23218 WeGIA has a SQL Injection endpoint 'adicionar_especie.php' parameter 'especie' — WeGIA 7.5 - 2025-01-20
CVE-2025-0579 Shiprocket Module REST API Module restapi sql injection — Shiprocket Module 7.3 High 2025-01-20
CVE-2025-0585 aEnrich Technology a+HRD - SQL Injection — a+HRD 9.8 Critical 2025-01-20
CVE-2025-0565 ZZCMS index.php sql injection — ZZCMS 7.3 High 2025-01-19
CVE-2025-0564 code-projects Fantasy-Cricket authenticate.php sql injection — Fantasy-Cricket 7.3 High 2025-01-19
CVE-2025-0563 code-projects Fantasy-Cricket update.php sql injection — Fantasy-Cricket 6.3 Medium 2025-01-19
CVE-2025-0562 Codezips Gym Management System health_status_entry.php sql injection — Gym Management System 6.3 Medium 2025-01-19
CVE-2025-0561 itsourcecode Farm Management System add-pig.php sql injection — Farm Management System 6.3 Medium 2025-01-18
CVE-2025-0558 TDuckCloud tduck-platform QueryProThemeRequest.java QueryProThemeRequest sql injection — tduck-platform 6.3 Medium 2025-01-18
CVE-2024-13184 The Ultimate WordPress Toolkit – WP Extended <= 3.0.12 - Unauthenticated SQL Injection via Login Attempts Module — The Ultimate WordPress Toolkit – WP Extended 7.5 High 2025-01-18
CVE-2025-0308 Ultimate Member <= 2.9.1 - Unauthenticated SQL Injection — Ultimate Member – User Profile, Registration, Login, Member Directory, Content Restriction & Membership Plugin 7.5 High 2025-01-18
CVE-2025-0541 Codezips Gym Management System edit_member.php sql injection — Gym Management System 6.3 Medium 2025-01-17
CVE-2025-0540 itsourcecode Tailoring Management System expadd.php sql injection — Tailoring Management System 6.3 Medium 2025-01-17
CVE-2025-0536 1000 Projects Attendance Tracking Management System edit_action.php sql injection — Attendance Tracking Management System 6.3 Medium 2025-01-17
CVE-2025-0535 Codezips Gym Management System edit_mem_submit.php sql injection — Gym Management System 6.3 Medium 2025-01-17
CVE-2025-0534 1000 Projects Campaign Management System Platform for Women loginnew.php sql injection — Campaign Management System Platform for Women 7.3 High 2025-01-17

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