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

Goal: 1000 CNY · Raised: 1336 CNY

100%

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

10002 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-2024-52335 Siemens Healthineers syngo 安全漏洞 — syngo.plaza VB30E 9.8 Critical2024-12-06
CVE-2024-51615 WordPress WordPress Auction Plugin plugin <= 3.7 - SQL Injection vulnerability — WordPress Auction Plugin 9.3 Critical2024-12-06
CVE-2024-53807 WordPress WP Mailster plugin <= 1.8.16.0 - SQL Injection vulnerability — WP Mailster 8.5 High2024-12-06
CVE-2024-53808 WordPress NEX-Forms plugin <= 8.7.8 - SQL Injection vulnerability — NEX-Forms 8.5 High2024-12-06
CVE-2024-53817 WordPress Acowebs Product Labels For Woocommerce plugin <= 1.5.8 - SQL Injection vulnerability — Product Labels For Woocommerce 7.6 High2024-12-06
CVE-2024-53815 WordPress Pinpoint Booking System plugin <= 2.9.9.5.2 - SQL Injection vulnerability — Pinpoint Booking System 8.5 High2024-12-06
CVE-2024-11729 KiviCare – Clinic & Patient Management System (EHR) <= 3.6.4 - Authenticated (Subscriber+) SQL Injection — KiviCare – Clinic & Patient Management System (EHR) 6.5 Medium2024-12-06
CVE-2024-11730 KiviCare – Clinic & Patient Management System (EHR) <= 3.6.4 - Authenticated (Doctor/Receptionist+) SQL Injection — KiviCare – Clinic & Patient Management System (EHR) 6.5 Medium2024-12-06
CVE-2024-11460 Verowa Connect <= 3.0.1 - Unauthenticated SQL Injection — Verowa Connect 7.5 High2024-12-06
CVE-2024-11728 KiviCare – Clinic & Patient Management System (EHR) <= 3.6.4 - Unauthenticated SQL Injection — KiviCare – Clinic & Patient Management System (EHR) 7.5 High2024-12-06
CVE-2024-10247 YouTube Gallery and Vimeo Gallery Plugin <= 2.4.2 - Authenticated (Administrator+) SQL Injection — Video Gallery – YouTube Gallery, Vimeo, Video Portfolio, Image Portfolio and Image Gallery 7.2 High2024-12-06
CVE-2024-12234 1000 Projects Beauty Parlour Management System edit-customer-detailed.php sql injection — Beauty Parlour Management System 7.3 High2024-12-05
CVE-2024-12231 CodeZips Project Management System index.php sql injection — Project Management System 7.3 High2024-12-05
CVE-2024-12230 PHPGurukul Complaint Management System subcategory.php sql injection — Complaint Management System 7.3 High2024-12-05
CVE-2024-12229 PHPGurukul Complaint Management System complaint-search.php sql injection — Complaint Management System 7.3 High2024-12-05
CVE-2024-12228 PHPGurukul Complaint Management System user-search.php sql injection — Complaint Management System 7.3 High2024-12-05
CVE-2024-12188 1000 Projects Library Management System stu.php sql injection — Library Management System 7.3 High2024-12-05
CVE-2024-12187 1000 Projects Library Management System showbook.php sql injection — Library Management System 7.3 High2024-12-05
CVE-2024-54221 WordPress FAT Services Booking plugin <= 5.6 - Unauthenticated SQL Injection vulnerability — FAT Services Booking 9.3 Critical2024-12-04
CVE-2024-11732 BP Profile Shortcodes Extra <= 2.6.0 - Authenticated (Contributor+) SQL Injection via tab Parameter — BP Profile Shortcodes Extra 6.5 Medium2024-12-03
CVE-2024-46905 WhatsUp Gold GetOrderByClause SQL Injection Privilege Escalation Vulnerability — WhatsUp Gold 8.8 High2024-12-02
CVE-2024-46906 WhatsUp Gold GetSqlWhereClause SQL Injection Privilege Escalation Vulnerability — WhatsUp Gold 8.8 High2024-12-02
CVE-2024-46907 WhatsUp Gold GetFilterCriteria SQL Injection Privilege Escalation Vulnerability — WhatsUp Gold 8.8 High2024-12-02
CVE-2024-46908 WhatsUp Gold GetFilterCriteria SQL Injection Privilege Escalation Vulnerability — WhatsUp Gold 8.8 High2024-12-02
CVE-2024-53792 WordPress Watu Quiz plugin <= 3.4.1.2 - SQL Injection vulnerability — Watu Quiz 8.5 High2024-12-02
CVE-2024-12015 SQL Injection in WordPress Project Manager Plugin — WP Project Manager 7.7 High2024-12-02
CVE-2024-12007 code-projects Farmacia visualizar-produto.php sql injection — Farmacia 6.3 Medium2024-12-01
CVE-2024-53783 WordPress Ni WooCommerce Cost Of Goods plugin <= 3.2.8 - SQL Injection vulnerability — Ni WooCommerce Cost Of Goods 7.6 High2024-11-30
CVE-2024-11998 code-projects Farmacia visualizer-forneccedor.chp sql injection — Farmacia 6.3 Medium2024-11-30
CVE-2024-11970 code-projects Concert Ticket Ordering System tour(cor).php sql injection — Concert Ticket Ordering System 7.3 High2024-11-28

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