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-0410 liujianview gymxmjpa MenberConntroller.java MenberDaoInpl sql injection — gymxmjpa 6.3 Medium 2025-01-13
CVE-2025-0409 liujianview gymxmjpa MembertypeController.java MembertypeDaoImpl sql injection — gymxmjpa 6.3 Medium 2025-01-13
CVE-2025-0408 liujianview gymxmjpa LoosController.java LoosDaoImpl sql injection — gymxmjpa 6.3 Medium 2025-01-13
CVE-2025-0407 liujianview gymxmjpa EquipmentController.java EquipmentDaoImpl sql injection — gymxmjpa 6.3 Medium 2025-01-13
CVE-2025-0406 liujianview gymxmjpa SubjectController.java SubjectDaoImpl sql injection — gymxmjpa 6.3 Medium 2025-01-13
CVE-2025-0405 liujianview gymxmjpa GoodsController.java GoodsDaoImpl sql injection — gymxmjpa 6.3 Medium 2025-01-13
CVE-2025-0404 liujianview gymxmjpa CoachController.java CoachController sql injection — gymxmjpa 6.3 Medium 2025-01-13
CVE-2025-0392 Guangzhou Huayi Intelligent Technology Jeewms graphReportController.do datagridGraph sql injection — Jeewms 6.3 Medium 2025-01-11
CVE-2025-0391 Guangzhou Huayi Intelligent Technology Jeewms CgFormBuildController. java saveOrUpdate sql injection — Jeewms 6.3 Medium 2025-01-11
CVE-2025-0103 Expedition: SQL Injection Vulnerability — Cloud NGFW 8.1 - 2025-01-11
CVE-2024-12404 CF Internal Link Shortcode <= 1.1.0 - Unauthenticated SQL Injection — CF Internal Link Shortcode 7.5 High 2025-01-11
CVE-2024-9134 Multiple SQL Injection vulnerabilities exist in the reporting application. A user with advanced report application access rights can exploit the SQL injection, allowing them to execute commands on the underlying operating system with elevated privileges. — Arista Edge Threat Management 8.3 High 2025-01-10
CVE-2024-12473 AI Scribe – SEO AI Writer, Content Generator, Humanizer, Blog Writer, SEO Optimizer, DALLE-3, AI WordPress Plugin ChatGPT (GPT-4o 128K) <= 2.5 - Authenticated (Contributor+) SQL Injection — Opace AI Scribe: SEO Content Creator & Humaizer for OpenAI & Anthropic 6.5 Medium 2025-01-10
CVE-2025-21628 Chatwoot has a Blind SQL-injection in Conversation and Contacts filters — chatwoot 9.1 Critical 2025-01-09
CVE-2025-22505 WordPress NC Wishlist for Woocommerce Plugin <= 1.0.1 - SQL Injection vulnerability — NC Wishlist for Woocommerce 8.5 High 2025-01-09
CVE-2025-22527 WordPress Mailing Group Listserv Plugin <= 2.0.9 - SQL Injection vulnerability — Mailing Group Listserv 7.6 High 2025-01-09
CVE-2025-22535 WordPress WPListCal Plugin <= 1.3.5 - SQL Injection vulnerability — WPListCal 8.5 High 2025-01-09
CVE-2025-22537 WordPress Google Maps Travel Route Plugin <= 1.3.1 - SQL Injection vulnerability — Google Maps Travel Route 8.5 High 2025-01-09
CVE-2025-22540 WordPress Emailing Subscription Plugin <= 1.4.1 - SQL Injection vulnerability — Emailing Subscription 9.3 Critical 2025-01-09
CVE-2025-22542 WordPress Virtual Bot Plugin <= 1.0.0 - SQL Injection vulnerability — Virtual Bot 9.3 Critical 2025-01-09
CVE-2024-12067 WP Travel – Ultimate Travel Booking System, Tour Management Engine <= 10.0.0 - Authenticated (Subscriber+) SQL Injection — WP Travel – Ultimate Travel Booking System, Tour Management Engine 6.5 Medium 2025-01-09
CVE-2025-0347 code-projects Admission Management System Login index.php sql injection — Admission Management System 7.3 High 2025-01-09
CVE-2025-0345 leiyuxi cy-fast listData sql injection — cy-fast 6.3 Medium 2025-01-09
CVE-2025-0344 leiyuxi cy-fast listData sql injection — cy-fast 6.3 Medium 2025-01-09
CVE-2025-0340 code-projects Cinema Seat Reservation System deleteBooking.php sql injection — Cinema Seat Reservation System 7.3 High 2025-01-09
CVE-2025-0336 Codezips Project Management System teacher.php sql injection — Project Management System 6.3 Medium 2025-01-09
CVE-2025-0334 leiyuxi cy-fast listData sql injection — cy-fast 6.3 Medium 2025-01-09
CVE-2025-0333 leiyuxi cy-fast listData sql injection — cy-fast 6.3 Medium 2025-01-09
CVE-2024-13204 kurniaramadhan E-Commerce-PHP blog-details.php sql injection — E-Commerce-PHP 5.5 Medium 2025-01-09
CVE-2024-13194 Sucms admin_members.php sql injection — Sucms 6.3 Medium 2025-01-08

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