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

Goal: 1000 CNY · Raised: 1000 CNY

100.0%

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

8957 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-2026-0565 code-projects Content Management System delete.php sql injection — Content Management System 7.3 High2026-01-02
CVE-2026-0546 code-projects Content Management System search.php sql injection — Content Management System 7.3 High2026-01-02
CVE-2025-15436 Yonyou KSOA work_edit.jsp sql injection — KSOA 7.3 High2026-01-02
CVE-2025-15435 Yonyou KSOA work_update.jsp sql injection — KSOA 7.3 High2026-01-02
CVE-2025-15434 Yonyou KSOA PrintZPYG.jsp sql injection — KSOA 7.3 High2026-01-02
CVE-2025-15425 Yonyou KSOA HTTP GET Parameter del_user.jsp sql injection — KSOA 7.3 High2026-01-02
CVE-2025-15424 Yonyou KSOA HTTP GET Parameter agent_worksdel.jsp sql injection — KSOA 7.3 High2026-01-02
CVE-2025-15421 Yonyou KSOA HTTP GET Parameter agent_worksadd.jsp sql injection — KSOA 7.3 High2026-01-02
CVE-2025-15420 Yonyou KSOA agent_work_report.jsp sql injection — KSOA 7.3 High2026-01-02
CVE-2025-15410 code-projects Online Guitar Store login.php sql injection — Online Guitar Store 7.3 High2026-01-01
CVE-2025-15409 code-projects Online Guitar Store Delete_product.php sql injection — Online Guitar Store 7.3 High2026-01-01
CVE-2025-55065 Kopek Reem ReKord Client SQL注入漏洞 — ReKord client 7.5 High2026-01-01
CVE-2025-15408 code-projects Online Guitar Store Create_product.php sql injection — Online Guitar Store 7.3 High2026-01-01
CVE-2025-15407 code-projects Online Guitar Store Create_category.php sql injection — Online Guitar Store 7.3 High2026-01-01
CVE-2026-0544 itsourcecode School Management System index.php sql injection — School Management System 7.3 High2026-01-01
CVE-2023-7331 PKrystian Full-Stack-Bank User sql injection — Full-Stack-Bank 4.7 Medium2025-12-31
CVE-2025-30628 WordPress Amazon Affiliates Addon for WPBakery Page Builder (formerly Visual Composer) plugin <= 1.2 - SQL Injection Vulnerability — Amazon Affiliates Addon for WPBakery Page Builder (formerly Visual Composer) 8.5 High2025-12-31
CVE-2025-28949 WordPress Mediabay - WordPress Media Library Folders <= 1.4 - SQL Injection Vulnerability — Mediabay - WordPress Media Library Folders 8.5 High2025-12-31
CVE-2025-15392 Kohana KodiCMS Search API Endpoint page.php like sql injection — KodiCMS 6.3 Medium2025-12-31
CVE-2023-54163 NLB mKlik Macedonia 3.3.12 SQL Injection via International Transfer Parameters — NLB mKlik Makedonija 7.5 High2025-12-30
CVE-2022-50694 SOUND4 IMPACT/FIRST/PULSE/Eco <=2.x SQL Injection via Username Parameter — Impact/Pulse/First 9.8 Critical2025-12-30
CVE-2025-15354 itsourcecode Society Management System add_admin.php sql injection — Society Management System 7.3 High2025-12-30
CVE-2025-15353 itsourcecode Society Management System edit_admin_query.php edit_admin_query sql injection — Society Management System 7.3 High2025-12-30
CVE-2025-15263 BiggiDroid Simple PHP CMS Admin Login login.php sql injection — Simple PHP CMS 7.3 High2025-12-30
CVE-2025-59129 WordPress Appointify plugin <= 1.0.8 - SQL Injection vulnerability — Appointify 7.6 High2025-12-30
CVE-2025-68990 WordPress BWL Pro Voting Manager plugin <= 1.4.9 - SQL Injection vulnerability — BWL Pro Voting Manager 8.5 High2025-12-30
CVE-2025-15243 code-projects Simple Stock System login.php sql injection — Simple Stock System 7.3 High2025-12-30
CVE-2025-15212 code-projects Refugee Food Management System regfood.php sql injection — Refugee Food Management System 6.3 Medium2025-12-30
CVE-2025-15211 code-projects Refugee Food Management System refugee.php sql injection — Refugee Food Management System 6.3 Medium2025-12-30
CVE-2025-15210 code-projects Refugee Food Management System editrefugee.php sql injection — Refugee Food Management System 6.3 Medium2025-12-29

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