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-79845 code-projects Simple Inventory System edit.php sql injection — Simple Inventory System 7.3 High 2026-08-25
CVE-2026-79804 SililaWijesinghe Food Ordering System search.php sql injection — Food Ordering System 7.3 High 2026-08-25
CVE-2026-75498 Webkul QloApps SQL injection — QloApps 7.2 High 2026-08-25
CVE-2026-75497 Webkul QloApps SQL injection — QloApps 7.2 High 2026-08-25
CVE-2026-78468 FluentCRM Pro <= 3.1.12 - Authenticated (Author+) SQL Injection — FluentCRM Pro – Email Newsletter, Automation, Email Marketing, Email Campaigns, Optins, Leads, and CRM Solution 6.5 Medium 2026-08-25
CVE-2026-78864 liketrek TREK Journey Entry Update journey.controller.t journeyService.updateEntry sql injection — TREK 6.3 Medium 2026-08-25
CVE-2026-77824 Media Sweep <= 1.1.3 - Authenticated (Administrator+) SQL Injection via 'fields' Parameter — Media Sweep – WordPress Media Cleaner 4.9 Medium 2026-08-25
CVE-2026-19949 All-in-One WP Migration and Backup <= 7.109 - Unauthenticated Second-Order SQL Injection via Archive Restore to Remote Code Execution — All-in-One WP Migration and Backup 8.8 High 2026-08-25
CVE-2026-78576 Readabler < 2.0.18 - Unauthenticated SQL Injection — Readabler 7.5 High 2026-08-25
CVE-2026-77137 SQL Injection in extension "Forms Export" (frp_form_answers) — Extension "Forms Export" 7.7 High 2026-08-25
CVE-2026-78568 Total Donations <= 2.0.5 - Unauthenticated SQL Injection — Total Donations 9.8 Critical 2026-08-25
CVE-2026-78656 itsourcecode Sales and Inventory System cust_del.php sql injection — Sales and Inventory System 6.3 Medium 2026-08-25
CVE-2026-78470 WP Project Manager Pro <= 4.0.1 - Authenticated (Subscriber+) SQL Injection — WP Project Manager Pro 6.5 Medium 2026-08-25
CVE-2026-15023 Events Manager <= 7.4.0 - Authenticated (Contributor+) SQL Injection via 'meta_key' Parameter in Event/Location Duplicate Action — Events Manager – Calendar, Bookings, Tickets, and more! 6.5 Medium 2026-08-25
CVE-2026-32555 WordPress Boost plugin <= 2.0.4 - SQL Injection vulnerability — Boost 9.3 Critical 2026-08-24
CVE-2026-32554 WordPress WooBeWoo Product Filter Pro plugin <= 3.1.8 - SQL Injection vulnerability — WooBeWoo Product Filter Pro 9.3 Critical 2026-08-24
CVE-2026-77635 CakePHP: FunctionsBuilder::jsonValue() vulerable to SQL injection with PostgresDriver — cakephp 9.2 Critical 2026-08-24
CVE-2026-76848 TypeORM 0.2.21 through 1.1.0 SQL Injection via SelectQueryBuilder.distinctOn — typeorm 7.5 High 2026-08-24
CVE-2026-78248 SourceCodester Simple Online Food Ordering System ajax.php save_settings sql injection — Simple Online Food Ordering System 7.3 High 2026-08-24
CVE-2026-78247 SourceCodester Simple Online Food Ordering System ajax.php confirm_order sql injection — Simple Online Food Ordering System 7.3 High 2026-08-24
CVE-2026-32551 WordPress Woo Essential plugin <= 4.3.0 - SQL Injection vulnerability — Woo Essential 9.3 Critical 2026-08-24
CVE-2026-32478 WordPress WP Project Manager Pro plugin <= 4.0.1 - SQL Injection vulnerability — WP Project Manager Pro 8.5 High 2026-08-24
CVE-2026-32471 WordPress ProLancer Element plugin <= 1.4.8 - SQL Injection vulnerability — ProLancer Element 8.5 High 2026-08-24
CVE-2026-78270 WordPress FluentCRM Pro plugin <= 3.1.12 - SQL Injection vulnerability — FluentCRM Pro 7.6 High 2026-08-24
CVE-2026-78246 itsourcecode Online Clinic Management System Admin Login login.php sql injection — Online Clinic Management System 7.3 High 2026-08-24
CVE-2026-78244 itsourcecode Real Estate Management System search.php sql injection — Real Estate Management System 7.3 High 2026-08-24
CVE-2026-78317 DIAEnergie - SQL Injection — DIAEnergie 8.8 High 2026-08-24
CVE-2026-78316 DIAEnergie - SQL Injection — DIAEnergie 8.8 High 2026-08-24
CVE-2026-78315 DIAEnergie - SQL Injection — DIAEnergie 8.8 High 2026-08-24
CVE-2026-78314 DIAEnergie - SQL Injection — DIAEnergie 8.8 High 2026-08-24

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