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

Goal: 1000 CNY · Raised: 1000 CNY

100.0%

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

9008 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-14536 code-projects Class and Exam Timetable Management Login index.php sql injection — Class and Exam Timetable Management 7.3 High2025-12-11
CVE-2025-13214 IBM Aspera Orchestrator SQL Injection — Aspera Orchestrator 7.6 High2025-12-11
CVE-2025-14529 Campcodes Retro Basketball Shoes Online Store admin_running.php sql injection — Retro Basketball Shoes Online Store 7.3 High2025-12-11
CVE-2025-14527 projectworlds Advanced Library Management System view_book.php sql injection — Advanced Library Management System 7.3 High2025-12-11
CVE-2025-14515 Campcodes Supplier Management System add_unit.php sql injection — Supplier Management System 7.3 High2025-12-11
CVE-2025-14514 Campcodes Supplier Management System add_distributor.php sql injection — Supplier Management System 7.3 High2025-12-11
CVE-2025-10163 List Category Posts <= 0.91.0 - Authenticated (Contributor+) SQL Injection via Plugin's Shortcode — List category posts 6.5 Medium2025-12-11
CVE-2025-67644 LangGraph SQLite Checkpoint is vulnerable to SQL Injection via metadata filter key in checkpointer list method — langgraph 7.3 High2025-12-10
CVE-2025-65950 WBCE CMS is Vulnerable to Time-Based Blind SQL Injection through groups[] Parameter — WBCE_CMS 8.8AIHighAI2025-12-10
CVE-2025-67501 WeGIA is vulnerable to SQL Injection via editar_categoria endpoint parameter — WeGIA 8.8AIHighAI2025-12-09
CVE-2021-47708 COMMAX Smart Home IoT Control System SQL Injection Authentication Bypass — Smart Home IoT Control System 9.8AICriticalAI2025-12-09
CVE-2021-47704 OpenBMCS SQL Injection via obix_test.php — OpenBMCS 6.5AIMediumAI2025-12-09
CVE-2025-14337 itsourcecode Student Management System new_grade.php sql injection — Student Management System 7.3 High2025-12-09
CVE-2025-14336 itsourcecode Student Management System promote.php sql injection — Student Management System 7.3 High2025-12-09
CVE-2025-14335 itsourcecode Student Management System new_school_year.php sql injection — Student Management System 7.3 High2025-12-09
CVE-2025-14334 itsourcecode Student Management System new_adviser.php sql injection — Student Management System 7.3 High2025-12-09
CVE-2025-64156 Fortinet FortiVoice SQL注入漏洞 — FortiVoice 6.8 High2025-12-09
CVE-2025-62093 WordPress Image&Video FullScreen Background plugin <= 1.6.7 - SQL Injection vulnerability — Image&Video FullScreen Background 8.5 High2025-12-09
CVE-2025-10655 Frappe Helpdesk 1.14.0 — SQL Injection in dashboard get_dashboard_data — Frappe HelpDesk 8.8AIHighAI2025-12-09
CVE-2025-12504 SQLi in Talent Software's UNIS — UNIS 9.8 Critical2025-12-09
CVE-2025-67520 WordPress Media Library Tools plugin <= 1.6.15 - SQL Injection vulnerability — Media Library Tools 7.6 High2025-12-09
CVE-2025-67518 WordPress Accordion Slider PRO plugin <= 1.2 - SQL Injection vulnerability — Accordion Slider PRO 8.5 High2025-12-09
CVE-2025-67519 WordPress Ninja Tables plugin <= 5.2.3 - SQL Injection vulnerability — Ninja Tables 7.6 High2025-12-09
CVE-2025-67517 WordPress ArtPlacer Widget plugin <= 2.22.9.2 - SQL Injection vulnerability — ArtPlacer Widget 8.5 High2025-12-09
CVE-2025-67516 WordPress Store Locator WordPress plugin <= 1.6.2 - SQL Injection vulnerability — Store Locator WordPress 8.5 High2025-12-09
CVE-2025-12807 FactoryTalk® DataMosaix™ Private Cloud SQL Injection — FactoryTalk® DataMosaix™ Private Cloud 8.8AIHighAI2025-12-09
CVE-2025-14285 code-projects Employee Profile Management System edit_personnel.php sql injection — Employee Profile Management System 7.3 High2025-12-09
CVE-2025-14259 Jihai Jshop MiniProgram Mall System api.html sql injection — Jshop MiniProgram Mall System 6.3 Medium2025-12-08
CVE-2025-14258 itsourcecode Student Management System newsubject.php sql injection — Student Management System 7.3 High2025-12-08
CVE-2025-14257 itsourcecode Student Management System newrecord.php sql injection — Student Management System 7.3 High2025-12-08

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