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

Goal: 1000 CNY · Raised: 1336 CNY

100%

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

10280 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-67877 ChurchCRM SQL Injection Vulnerability — CRM 8.8AI High AI 2025-12-17
CVE-2025-66396 ChurchCRM has SQL Injection in User Editor via `type` Parameter Key — CRM 7.2 High 2025-12-17
CVE-2025-66395 SQL Injection in Event List via `WhichType` Parameter — CRM 8.8 High 2025-12-17
CVE-2025-14780 Xiongwei Smart Catering Cloud Platform dish_trade_detail_get sql injection — Smart Catering Cloud Platform 6.3 Medium 2025-12-16
CVE-2025-68056 WordPress LBG Zoominoutslider plugin <= 5.4.4 - SQL Injection vulnerability — LBG Zoominoutslider 8.5 High 2025-12-16
CVE-2025-68053 WordPress xPromoter plugin <= 1.3.4 - SQL Injection vulnerability — xPromoter 8.5 High 2025-12-16
CVE-2025-68055 WordPress Hydra Booking plugin <= 1.1.32 - SQL Injection vulnerability — Hydra Booking 8.5 High 2025-12-16
CVE-2025-68054 WordPress CountDown With Image or Video Background plugin <= 1.5 - SQL Injection vulnerability — CountDown With Image or Video Background 8.5 High 2025-12-16
CVE-2025-67999 WordPress Newsletter plugin <= 9.0.9 - SQL Injection vulnerability — Newsletter 7.6 High 2025-12-16
CVE-2025-67962 WordPress Broken Link Checker plugin <= 1.2.6 - SQL Injection vulnerability — Broken Link Checker 7.6 High 2025-12-16
CVE-2025-67950 WordPress All In One SEO Pack plugin <= 4.9.1 - SQL Injection vulnerability — All In One SEO Pack 8.5 High 2025-12-16
CVE-2025-62849 QTS, QuTS hero — QTS 9.8AI Critical AI 2025-12-16
CVE-2025-67751 ChurchCRM has SQL Injection in Event Editor via `EN_tyid` Parameter caused by an Incomplete Fix — CRM 7.2 High 2025-12-16
CVE-2025-67736 Authenticated SQL Injection in FreePBX tts (Text To Speech) module — tts 7.2AI High AI 2025-12-16
CVE-2023-53877 Bus Reservation System 1.1 Multiple SQL Injection via pickup_id Parameter — Bus Reservation System 9.1AI Critical AI 2025-12-15
CVE-2025-34179 NetSupport Manager < 14.12.0001 Unauthenticated SQLi Local File Disclosure — Manager 9.1AI Critical AI 2025-12-15
CVE-2025-14383 Booking Calendar <= 10.14.8 - Unauthenticated SQL Injection via dates_to_check — Booking Calendar 7.5 High 2025-12-15
CVE-2025-14711 FantasticLBP Hotels Server hotelList.php sql injection — Hotels Server 7.3 High 2025-12-15
CVE-2025-14710 FantasticLBP Hotels Server OrderList.php sql injection — Hotels Server 7.3 High 2025-12-15
CVE-2025-14694 ketr JEPaaS readAllPostil sql injection — JEPaaS 4.7 Medium 2025-12-15
CVE-2025-14668 campcodes Advanced Online Examination System loginExe.php sql injection — Advanced Online Examination System 7.3 High 2025-12-14
CVE-2025-14667 itsourcecode COVID Tracking System page sql injection — COVID Tracking System 7.3 High 2025-12-14
CVE-2025-14666 itsourcecode COVID Tracking System page sql injection — COVID Tracking System 7.3 High 2025-12-14
CVE-2025-14664 Campcodes Supplier Management System view_unit.php sql injection — Supplier Management System 7.3 High 2025-12-14
CVE-2025-14661 itsourcecode Student Managemen System advisers.php sql injection — Student Managemen System 7.3 High 2025-12-14
CVE-2025-14653 itsourcecode Student Management System addrecord.php sql injection — Student Management System 7.3 High 2025-12-14
CVE-2025-14652 itsourcecode Online Cake Ordering System admindetail.php sql injection — Online Cake Ordering System 7.3 High 2025-12-14
CVE-2025-14650 itsourcecode Online Cake Ordering System product.php sql injection — Online Cake Ordering System 7.3 High 2025-12-14
CVE-2025-14649 itsourcecode Online Cake Ordering System supplier.php sql injection — Online Cake Ordering System 7.3 High 2025-12-14
CVE-2025-14647 code-projects Computer Book Store admin_delete.php sql injection — Computer Book Store 7.3 High 2025-12-14

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