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-2015-20121 RealtyScript 4.0.2 SQL Injection via u_id and agent Parameters — RealtyScripts 8.2 High2026-03-15
CVE-2026-4173 CodePhiliaX Chat2DB Database Export DMDBManage.java updateProcedure sql injection — Chat2DB 6.3 Medium2026-03-15
CVE-2026-32628 AnythingLLM has SQL Injection in Built-in SQL Agent Plugin via Unsanitized table_name Parameter — anything-llm 8.8 -2026-03-13
CVE-2025-36368 IBM Sterling B2B Integrator and IBM Sterling File Gateway SQL Injection — Sterling B2B Integrator 6.5 Medium2026-03-13
CVE-2026-32458 WordPress WOLF plugin <= 1.0.8.7 - SQL Injection vulnerability — WOLF 7.6 High2026-03-13
CVE-2026-32459 WordPress UpsellWP plugin <= 2.2.4 - SQL Injection vulnerability — UpsellWP 7.6 High2026-03-13
CVE-2026-32433 WordPress CP Contact Form with Paypal plugin <= 1.3.61 - SQL Injection vulnerability — CP Contact Form with Paypal 8.5 High2026-03-13
CVE-2026-32422 WordPress WP EasyCart plugin <= 5.8.13 - SQL Injection vulnerability — WP EasyCart 8.5 High2026-03-13
CVE-2026-32418 WordPress Meow Gallery plugin <= 5.4.4 - SQL Injection vulnerability — Meow Gallery 7.6 High2026-03-13
CVE-2026-32399 WordPress Media LIbrary Assistant plugin <= 3.32 - SQL Injection vulnerability — Media LIbrary Assistant 8.5 High2026-03-13
CVE-2026-32368 WordPress Geo to Lat plugin <= 1.0.19 - SQL Injection vulnerability — Geo to Lat 8.5 High2026-03-13
CVE-2026-32366 WordPress Collapsing Categories plugin <= 3.0.9 - SQL Injection vulnerability — Collapsing Categories 8.5 High2026-03-13
CVE-2026-32365 WordPress Collapsing Archives plugin <= 3.0.7 - SQL Injection vulnerability — Collapsing Archives 8.5 High2026-03-13
CVE-2026-32358 WordPress Booking Calendar plugin <= 10.14.15 - SQL Injection vulnerability — Booking Calendar 7.6 High2026-03-13
CVE-2026-31922 WordPress Fox LMS plugin <= 1.0.6.3 - SQL Injection vulnerability — Fox LMS 8.5 High2026-03-13
CVE-2026-31917 WordPress WP ERP plugin <= 1.16.10 - SQL Injection vulnerability — WP ERP 8.5 High2026-03-13
CVE-2026-22193 wpDiscuz before 7.6.47 - SQL Injection in getAllSubscriptions() — wpDiscuz 8.1 High2026-03-13
CVE-2026-32306 OneUptime ClickHouse SQL Injection via Aggregate Query Parameters — oneuptime 10.0 Critical2026-03-12
CVE-2026-25076 Anchore Enterprise GraphQL Reports API SQL injection — Anchore Enterprise 7.3 High2026-03-12
CVE-2026-32137 DataEase SQL Injection Vulnerability — dataease 9.8AICriticalAI2026-03-12
CVE-2026-21708 Veeam Backup And Replication 安全漏洞 — Backup and Replication 8.8AIHighAI2026-03-12
CVE-2019-25543 Netartmedia Real Estate Portal 5.0 SQL Injection via index.php — Netartmedia Real Estate Portal 8.2 High2026-03-12
CVE-2019-25542 Netartmedia Real Estate Portal 5.0 SQL Injection via index.php — Netartmedia Real Estate Portal 8.2 High2026-03-12
CVE-2019-25541 Netartmedia PHP Mall 4.1 Multiple SQL Injection — Netartmedia PHP Mall 8.2 High2026-03-12
CVE-2019-25540 Netartmedia PHP Mall 4.1 Multiple SQL Injection — Netartmedia PHP Mall 8.2 High2026-03-12
CVE-2019-25539 202CMS v10 beta SQL Injection via register.php — 202CMS 8.2 High2026-03-12
CVE-2019-25538 202CMS v10 beta SQL Injection via log_user Parameter — 202CMS 8.2 High2026-03-12
CVE-2019-25537 Netartmedia Event Portal 2.0 SQL Injection via loginaction.php — Netartmedia Event Portal 8.2 High2026-03-12
CVE-2019-25536 Netartmedia PHP Real Estate Agency 4.0 SQL Injection via features parameter — Netartmedia PHP Real Estate Agency 8.2 High2026-03-12
CVE-2019-25535 Netartmedia PHP Dating Site SQL Injection via loginaction.php — Netartmedia Php Dating Site 8.2 High2026-03-12

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