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

Goal: 1000 CNY · Raised: 1336 CNY

100%

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

10262 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-2023-36677 WordPress SP Project & Document Manager Plugin <= 4.67 is vulnerable to SQL Injection — SP Project & Document Manager 8.3 High 2023-11-03
CVE-2023-36529 WordPress Houzez CRM Plugin <= 1.3.4 is vulnerable to SQL Injection — Houzez - Real Estate WordPress Theme 9.9 Critical 2023-11-03
CVE-2023-34179 WordPress Groundhogg Plugin <= 2.7.11 is vulnerable to SQL Injection — Groundhogg 7.6 High 2023-11-03
CVE-2023-25700 WordPress Tutor LMS Plugin <= 2.1.10 is vulnerable to SQL Injection — Tutor LMS 8.2 High 2023-11-03
CVE-2023-25800 WordPress Tutor LMS Plugin <= 2.2.0 is vulnerable to SQL Injection — Tutor LMS 8.1 High 2023-11-03
CVE-2023-25990 WordPress Tutor LMS Plugin <= 2.1.10 is vulnerable to SQL Injection — Tutor LMS 7.1 High 2023-11-03
CVE-2023-32508 WordPress Order Your Posts Manually Plugin <= 2.2.5 is vulnerable to SQL Injection — Order Your Posts Manually 7.6 High 2023-11-03
CVE-2023-32121 WordPress Zero Spam Plugin <= 5.4.4 is vulnerable to SQL Injection — Zero Spam for WordPress 7.6 High 2023-11-03
CVE-2022-46818 WordPress Email posts to subscribers Plugin <= 6.2 is vulnerable to SQL Injection — Email posts to subscribers 8.2 High 2023-11-03
CVE-2022-47426 WordPress Neshan Maps Plugin <= 1.1.4 is vulnerable to SQL Injection — Neshan Maps 6.0 Medium 2023-11-03
CVE-2022-46859 WordPress Spiffy Calendar Plugin <= 4.9.1 is vulnerable to SQL Injection — Spiffy Calendar 8.5 High 2023-11-03
CVE-2023-26015 WordPress MapPress Maps for WordPress Plugin <= 2.85.4 is vulnerable to SQL Injection — MapPress Maps for WordPress 7.1 High 2023-11-03
CVE-2022-46808 WordPress ARMember Plugin <= 3.4.11 is vulnerable to SQL Injection — ARMember 8.2 High 2023-11-03
CVE-2022-47445 WordPress Be POPIA Compliant Plugin <= 1.2.0 is vulnerable to SQL Injection — Be POPIA Compliant 8.2 High 2023-11-03
CVE-2023-25960 WordPress Zendrop – Global Dropshipping Plugin <= 1.0.0 is vulnerable to SQL Injection — Zendrop – Global Dropshipping 10.0 Critical 2023-11-03
CVE-2022-45805 WordPress Paytm Payment Gateway Plugin <= 2.7.3 is vulnerable to SQL Injection — Paytm Payment Gateway 8.2 High 2023-11-03
CVE-2022-47588 WordPress Simple Photo Gallery Plugin <= v1.8.1 is vulnerable to SQL Injection — Simple Photo Gallery 6.7 Medium 2023-11-03
CVE-2023-34383 WordPress WP Project Manager Plugin <= 2.6.0 is vulnerable to SQL Injection — WP Project Manager 8.5 High 2023-11-03
CVE-2023-41652 WordPress RSVPMarker Plugin <= 10.6.6 is vulnerable to SQL Injection — RSVPMaker 8.2 High 2023-11-03
CVE-2023-5929 Campcodes Simple Student Information System manage_academic.php sql injection — Simple Student Information System 5.5 Medium 2023-11-02
CVE-2023-5928 Campcodes Simple Student Information System manage_department.php sql injection — Simple Student Information System 5.5 Medium 2023-11-02
CVE-2023-5927 Campcodes Simple Student Information System manage_course.php sql injection — Simple Student Information System 5.5 Medium 2023-11-02
CVE-2023-5926 Campcodes Simple Student Information System update_status.php sql injection — Simple Student Information System 5.5 Medium 2023-11-02
CVE-2023-5925 Campcodes Simple Student Information System Master.php sql injection — Simple Student Information System 5.5 Medium 2023-11-02
CVE-2023-5924 Campcodes Simple Student Information System view_course.php sql injection — Simple Student Information System 5.5 Medium 2023-11-02
CVE-2023-5923 Campcodes Simple Student Information System index.php sql injection — Simple Student Information System 5.5 Medium 2023-11-02
CVE-2023-45347 Online Food Ordering System v1.0 - Multiple Unauthenticated SQL Injections (SQLi) — Online Food Ordering System 9.8 Critical 2023-11-02
CVE-2023-45346 Online Food Ordering System v1.0 - Multiple Unauthenticated SQL Injections (SQLi) — Online Food Ordering System 9.8 Critical 2023-11-02
CVE-2023-45345 Online Food Ordering System v1.0 - Multiple Unauthenticated SQL Injections (SQLi) — Online Food Ordering System 9.8 Critical 2023-11-02
CVE-2023-45338 Online Food Ordering System v1.0 - Multiple Unauthenticated SQL Injections (SQLi) — Online Food Ordering System 9.8 Critical 2023-11-02

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