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

Goal: 1000 CNY · Raised: 1336 CNY

100%

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

10268 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-0533 1000 Projects Campaign Management System Platform for Women sc_login.php sql injection — Campaign Management System Platform for Women 7.3 High 2025-01-17
CVE-2025-0532 Codezips Gym Management System new_submit.php sql injection — Gym Management System 6.3 Medium 2025-01-17
CVE-2025-0531 code-projects Chat System leaveroom.php sql injection — Chat System 6.3 Medium 2025-01-17
CVE-2025-0527 code-projects Admission Management System signupconfirm.php sql injection — Admission Management System 7.3 High 2025-01-17
CVE-2025-23912 WordPress WordPress Custom Sidebar Plugin <= 2.3 - SQL Injection vulnerability — WordPress Custom Sidebar 8.5 High 2025-01-16
CVE-2025-23913 WordPress Google Map Professional Plugin <= 1.0 - SQL Injection vulnerability — WordPress Google Map Professional 8.5 High 2025-01-16
CVE-2025-23911 WordPress Solidres – Hotel booking plugin for WordPress Plugin <= 0.9.4 - SQL Injection vulnerability — Solidres – Hotel booking plugin 8.5 High 2025-01-16
CVE-2025-23780 WordPress Easy Code Snippets Plugin <= 1.0.2 - SQL Injection vulnerability — Easy Code Snippets 7.6 High 2025-01-16
CVE-2025-23779 WordPress ResAds Plugin <= 2.0.5 - SQL Injection vulnerability — ResAds 7.6 High 2025-01-16
CVE-2024-12614 Passwords Manager <= 1.4.8 - Missing Authorization to Authenticated (Subscriber+) Add Password + Update Encryption Key — Passwords Manager 7.5 High 2025-01-16
CVE-2024-12613 Passwords Manager <= 1.4.8 - Unauthenticated SQL Injection — Passwords Manager 7.5 High 2025-01-16
CVE-2024-12615 Passwords Manager <= 1.4.8 - Authenticated (Subscriber+) SQL Injection — Passwords Manager 6.5 Medium 2025-01-16
CVE-2025-0455 NetVision Information airPASS - SQL injection — airPASS 9.8 Critical 2025-01-16
CVE-2025-0491 Fanli2012 native-php-cms cat_dodel.php sql injection — native-php-cms 6.3 Medium 2025-01-15
CVE-2025-0490 Fanli2012 native-php-cms article_dodel.php sql injection — native-php-cms 6.3 Medium 2025-01-15
CVE-2025-0489 Fanli2012 native-php-cms friendlink_dodel.php sql injection — native-php-cms 6.3 Medium 2025-01-15
CVE-2025-0488 Fanli2012 native-php-cms product_list.php sql injection — native-php-cms 6.3 Medium 2025-01-15
CVE-2025-0487 Fanli2012 native-php-cms cat_edit.php sql injection — native-php-cms 6.3 Medium 2025-01-15
CVE-2025-0486 Fanli2012 native-php-cms login.php sql injection — native-php-cms 7.3 High 2025-01-15
CVE-2025-22785 WordPress Course Booking System plugin <= 6.0.6 - SQL Injection vulnerability — Course Booking System 9.3 Critical 2025-01-15
CVE-2025-22799 WordPress Neon Product Designer Plugin <= 2.2.0 - SQL Injection vulnerability — Neon Product Designer 8.5 High 2025-01-15
CVE-2024-13162 Ivanti EPM SQL注入漏洞 — Endpoint Manager 7.2 High 2025-01-14
CVE-2025-0462 Shanghai Lingdang Information Technology Lingdang CRM index.php sql injection — Lingdang CRM 6.3 Medium 2025-01-14
CVE-2023-37931 Fortinet FortiVoice Entreprise SQL注入漏洞 — FortiVoice 8.6 High 2025-01-14
CVE-2024-35278 Fortinet FortiPortal SQL注入漏洞 — FortiPortal 4.1 Medium 2025-01-14
CVE-2024-52969 Fortinet FortiSIEM SQL注入漏洞 — FortiSIEM 3.7 Medium 2025-01-14
CVE-2024-35275 Fortinet FortiManager和Fortinet FortiAnalyzer SQL注入漏洞 — FortiManager 6.5 Medium 2025-01-14
CVE-2024-55593 Fortinet FortiWeb SQL注入漏洞 — FortiWeb 2.6 Low 2025-01-14
CVE-2025-20620 STEALTHONE多款产品 SQL注入漏洞 — STEALTHONE D220 7.5 High 2025-01-14
CVE-2025-0063 SQL Injection vulnerability in SAP NetWeaver AS for ABAP and ABAP Platform — SAP NetWeaver AS ABAP and ABAP Platform 8.8 High 2025-01-14

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