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

Goal: 1000 CNY · Raised: 1336 CNY

100%

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

10247 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-2026-65494 WordPress Dokan Pro plugin <= 5.0.2 - SQL Injection vulnerability — Dokan Pro 7.1 High 2026-07-23
CVE-2026-65462 WordPress Uncanny Automator plugin <= 7.3.2 - SQL Injection vulnerability — Uncanny Automator 7.6 High 2026-07-23
CVE-2026-65454 WordPress Quiz And Survey Master plugin <= 11.2.0 - SQL Injection vulnerability — Quiz And Survey Master 8.5 High 2026-07-23
CVE-2026-65450 WordPress MapSVG plugin <= 8.14.0 - SQL Injection vulnerability — MapSVG 8.5 High 2026-07-23
CVE-2026-65451 WordPress MapSVG plugin <= 8.14.0 - SQL Injection vulnerability — MapSVG 8.5 High 2026-07-23
CVE-2026-61949 WordPress Bookly plugin <= 27.7 - SQL Injection vulnerability — Bookly 9.3 Critical 2026-07-23
CVE-2026-61950 WordPress TrueBooker plugin <= 1.2.3 - SQL Injection vulnerability — TrueBooker 9.3 Critical 2026-07-23
CVE-2026-61948 WordPress WPDM – Premium Packages plugin <= 6.2.0 - SQL Injection vulnerability — WPDM – Premium Packages 9.3 Critical 2026-07-23
CVE-2026-59526 WordPress MapSVG plugin <= 8.14.0 - SQL Injection vulnerability — MapSVG 9.3 Critical 2026-07-23
CVE-2026-59525 WordPress Participants Database plugin <= 2.7.8.3 - SQL Injection vulnerability — Participants Database 9.3 Critical 2026-07-23
CVE-2026-59514 WordPress Buddyboss Platform plugin <= 3.0.5 - SQL Injection vulnerability — Buddyboss Platform 9.3 Critical 2026-07-23
CVE-2026-25405 WordPress eRoom plugin <= 1.7.1 - SQL Injection vulnerability — eRoom 8.5 High 2026-07-23
CVE-2026-24552 WordPress Create plugin <= 2.5.3 - SQL Injection vulnerability — Create 8.5 High 2026-07-23
CVE-2026-15448 Tickera <= 3.6.0.1 - Authenticated (Staff+) SQL Injection via 'tc_order_status_filter' Parameter — Tickera – Sell Tickets & Manage Events 6.5 Medium 2026-07-23
CVE-2026-13119 Registrations for the Events Calendar <= 3.2 - Authenticated (Contributor+) SQL Injection via 'standard' Parameter — Registrations for the Events Calendar – Event Registration Plugin 6.5 Medium 2026-07-23
CVE-2026-13009 AI Copilot <= 1.5.4 - Authenticated (Subscriber+) SQL Injection via 'order[0][dir]' Parameter — AI Copilot – Content Generator 6.5 Medium 2026-07-23
CVE-2026-15906 Premium Packages <= 7.0.4 - Authenticated (Admin+) SQL Injection via 'orderby' Parameter — Premium Packages – Sell Digital Products Securely 6.5 Medium 2026-07-23
CVE-2026-15761 Tickera <= 3.6.0.1 - Authenticated (Staff+) SQL Injection via 'tc_event_filter' Parameter — Tickera – Sell Tickets & Manage Events 6.5 Medium 2026-07-23
CVE-2026-9713 Product Designer for WooCommerce WordPress | Lumise <= 2.1.1 - Unauthenticated SQL Injection via 'id' Parameter in Cart JSON Upload — Product Designer for WooCommerce WordPress | Lumise 7.5 High 2026-07-23
CVE-2026-2395 SQLi in Xpoda Türkiye Informatics Technology's No Code Platform — No Code Platform 9.8 Critical 2026-07-22
CVE-2026-16490 itsourcecode Hospital Management System prescription.php sql injection — Hospital Management System 6.3 Medium 2026-07-22
CVE-2026-16484 SourceCodester Class and Exam Timetabling System edit_subjecta.php sql injection — Class and Exam Timetabling System 7.3 High 2026-07-21
CVE-2026-63080 Aptabase SQL Injection via ClickHouse query backend — aptabase 6.5 Medium 2026-07-21
CVE-2026-64880 Blind SQL Injection — Security Center 7.1 High 2026-07-21
CVE-2016-20096 Linknat VOS3000/VOS2009 2.1.2.0 SQL Injection via login.jsp — Linknat VOS3000 9.8 Critical 2026-07-21
CVE-2026-55082 DHIS2 SQL injection in SQL View filter values — dhis2-core - - 2026-07-21
CVE-2026-55084 SQL Injection in SqlView Filter Parameter Leading to Arbitrary Database Read — dhis2-core 8.8 High 2026-07-21
CVE-2026-15829 SQL Injection and Security Boundary Bypass in googleapis/mcp-toolbox — MCP Toolbox for Databases (googleapis/mcp-toolbox) - - 2026-07-21
CVE-2026-16449 zsadmin2025 ZS-Admin com.zs.sys.dept.controller.SysDeptController page OrderItem.desc sql injection — ZS-Admin 6.3 Medium 2026-07-21
CVE-2026-1617 SQLi in Turkmesh's Turkhotspot 5651 Loglama — Turkhotspot 5651 Loglama 9.8 Critical 2026-07-21

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