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

Goal: 1000 CNY · Raised: 1359 CNY

100%

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

10927 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-105317 WordPress Paid Member Subscriptions plugin <= 3.1.1 - SQL Injection vulnerability — Paid Member Subscriptions 8.5 High 2026-10-06
CVE-2026-42417 WordPress ARMember Premium plugin <= 7.8 - SQL Injection vulnerability — ARMember Premium 9.3 Critical 2026-10-06
CVE-2026-42416 WordPress UDesign Core plugin <= 4.15.0 - SQL Injection vulnerability — UDesign Core 8.5 High 2026-10-06
CVE-2026-42415 WordPress Porto Theme - Functionality plugin <= 3.9.3 - SQL Injection vulnerability — Porto Theme - Functionality 9.3 Critical 2026-10-06
CVE-2026-42414 WordPress ListingPro plugin <= 2.9.12 - SQL Injection vulnerability — ListingPro 8.5 High 2026-10-06
CVE-2026-41555 WordPress Newsletter Subscription Form – User Subscriptions Form, Capture Email plugin <= 1.5.9 - SQL Injection vulnerability — Newsletter Subscription Form – User Subscriptions Form, Capture Email 9.3 Critical 2026-10-06
CVE-2026-39795 WordPress SendPress Newsletters plugin <= 1.26.1.20 - SQL Injection vulnerability — SendPress Newsletters 9.3 Critical 2026-10-06
CVE-2026-39785 WordPress Gmedia Photo Gallery plugin <= 1.25.1 - SQL Injection vulnerability — Gmedia Photo Gallery 9.3 Critical 2026-10-06
CVE-2026-39771 WordPress Buddyboss Platform plugin <= 3.1.0 - SQL Injection vulnerability — Buddyboss Platform 8.5 High 2026-10-06
CVE-2026-39764 WordPress Radius Booking — Booking Calendar for Appointments & Services plugin <= 1.0.19 - SQL Injection vulnerability — Radius Booking — Booking Calendar for Appointments &amp; Services 9.3 Critical 2026-10-06
CVE-2026-39747 WordPress Woffice theme <= 5.4.35 - SQL Injection vulnerability — Woffice 8.5 High 2026-10-06
CVE-2026-39746 WordPress Booknetic plugin <= 4.8.5 - SQL Injection vulnerability — Booknetic 9.3 Critical 2026-10-06
CVE-2026-32581 WordPress Mooberry Book Manager plugin 4.16.2 - SQL Injection vulnerability — Mooberry Book Manager 7.1 High 2026-10-06
CVE-2026-32580 WordPress WooCommerce Lottery plugin <= 2.2.9 - SQL Injection vulnerability — WooCommerce Lottery 7.5 High 2026-10-06
CVE-2026-32557 WordPress WooCommerce Appointments plugin <= 5.3.2 - SQL Injection vulnerability — WooCommerce Appointments 9.3 Critical 2026-10-06
CVE-2026-25434 WordPress WP2LEADS plugin <= 3.5.7 - SQL Injection vulnerability — WP2LEADS 8.5 High 2026-10-06
CVE-2026-4889 SQL Injection (SQLi) in eLoanApp Platform by RDL Technologies — eLoanApp Platform 7.8 High 2026-10-06
CVE-2026-105807 SourceCodester Simple Student Information System searchquery.php sql injection — Simple Student Information System 7.3 High 2026-10-06
CVE-2026-105776 bhagya3929 Employee-Movement-Tracking-and-Monitoring-Website-for-IOCL admin_transaction.php sql injection — Employee-Movement-Tracking-and-Monitoring-Website-for-IOCL 7.3 High 2026-10-06
CVE-2026-105472 girishsaraf Online-Appointment-Booking-System Booking book.php sql injection — Online-Appointment-Booking-System 6.3 Medium 2026-10-06
CVE-2026-105471 girishsaraf Online-Appointment-Booking-System Registration signup.php sql injection — Online-Appointment-Booking-System 7.3 High 2026-10-05
CVE-2026-105470 girishsaraf Online-Appointment-Booking-System Doctor Search Endpoint locateus.php mysqli_query sql injection — Online-Appointment-Booking-System 7.3 High 2026-10-05
CVE-2026-105469 girishsaraf Online-Appointment-Booking-System AJAX Endpoint get_town.php sql injection — Online-Appointment-Booking-System 7.3 High 2026-10-05
CVE-2026-105468 girishsaraf Online-Appointment-Booking-System Login mlogin.php mysqli_query sql injection — Online-Appointment-Booking-System 7.3 High 2026-10-05
CVE-2026-105388 feelec-yishu feelcrm-os Member Endpoint MemberController.class.php index sql injection — feelcrm-os 6.3 Medium 2026-10-05
CVE-2026-71298 Maestro: sql identifier injection via properties.* search filter and orderby field — Multicluster Engine for Kubernetes 6.4 Medium 2026-10-05
CVE-2026-103066 WordPress WP BASE Booking plugin <= 6.4.0 - SQL Injection vulnerability — WP BASE Booking 8.5 High 2026-10-05
CVE-2026-105387 girishsaraf Online-Appointment-Booking-System Patient Login cover.php mysqli_query sql injection — Online-Appointment-Booking-System 7.3 High 2026-10-05
CVE-2026-105386 onetwothreeneth HospitalManagementSystem print.php get sql injection — HospitalManagementSystem 7.3 High 2026-10-05
CVE-2026-103352 WordPress WP BASE Booking plugin <= 6.4.0 - SQL Injection vulnerability — WP BASE Booking 9.3 Critical 2026-10-05

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