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-2019-25534 Netartmedia PHP Car Dealer SQL Injection via features parameter — Netartmedia PHP Car Dealer 8.2 High2026-03-12
CVE-2019-25533 Netartmedia PHP Business Directory 4.2 SQL Injection via loginaction.php — Netartmedia PHP Business Directory 8.2 High2026-03-12
CVE-2019-25532 Netartmedia Jobs Portal 6.1 SQL Injection via loginaction.php — Netartmedia Jobs Portal 8.2 High2026-03-12
CVE-2019-25531 Netartmedia Deals Portal Lastest SQL Injection via loginaction.php — Netartmedia Deals Portal 8.2 High2026-03-12
CVE-2019-25530 uHotelBooking System Lastest SQL Injection via system_page Parameter — uHotelBooking System 8.2 High2026-03-12
CVE-2019-25529 Placeto CMS Alpha rv.4 SQL Injection via page Parameter — Placeto CMS 7.1 High2026-03-12
CVE-2019-25527 Inout EasyRooms Ultimate Edition v1.0 SQL Injection via searchdetailed — Inout EasyRooms Ultimate Edition 8.2 High2026-03-12
CVE-2019-25528 Inout EasyRooms Ultimate Edition v1.0 SQL Injection via search — Inout EasyRooms Ultimate Edition 8.2 High2026-03-12
CVE-2019-25526 Inout EasyRooms Ultimate Edition v1.0 SQL Injection via search — Inout EasyRooms Ultimate Edition 8.2 High2026-03-12
CVE-2019-25525 Inout EasyRooms Ultimate Edition v1.0 SQL Injection via search — Inout EasyRooms Ultimate Edition 8.2 High2026-03-12
CVE-2019-25524 XooGallery Lastest Latest SQL Injection via results.php — XooGallery 8.2 High2026-03-12
CVE-2019-25523 XooGallery Lastest Latest SQL Injection via cat.php — XooGallery 8.2 High2026-03-12
CVE-2019-25522 XooGallery Lastest Latest Multiple SQL Injections via photo.php — XooGallery 8.2 High2026-03-12
CVE-2019-25521 XooGallery Lastest Latest SQL Injection via gal.php gal_id — XooGallery 8.2 High2026-03-12
CVE-2019-25520 Jettweb PHP Hazir Haber Sitesi Scripti V1 Authentication Bypass — Hazir Haber Sitesi Scripti 8.2 High2026-03-12
CVE-2019-25519 Jettweb PHP Hazir Haber Sitesi Scripti V1 SQL Injection — Hazir Haber Sitesi Scripti 8.2 High2026-03-12
CVE-2019-25518 Jettweb PHP Hazir Haber Sitesi Scripti V1 SQL Injection via arama.php — Hazir Haber Sitesi Scripti 8.2 High2026-03-12
CVE-2019-25517 Jettweb PHP Hazir Haber Sitesi Scripti V1 SQL Injection via haberarsiv.php — Hazir Haber Sitesi Scripti 8.2 High2026-03-12
CVE-2019-25516 Jettweb PHP Hazir Haber Sitesi Scripti V1 SQL Injection via gallery.php — Hazir Haber Sitesi Scripti 8.2 High2026-03-12
CVE-2019-25515 Jettweb PHP Hazir Haber Sitesi Scripti V3 Authentication Bypass — Hazir Haber Sitesi Scripti 7.5 High2026-03-12
CVE-2019-25514 Jettweb PHP Hazir Haber Sitesi Scripti V3 SQL Injection — Hazir Haber Sitesi Scripti 8.2 High2026-03-12
CVE-2019-25513 Jettweb PHP Hazir Haber Sitesi Scripti V3 SQL Injection via datagetir.php — Hazir Haber Sitesi Scripti 8.2 High2026-03-12
CVE-2019-25512 Jettweb PHP Hazir Haber Sitesi Scripti V3 SQL Injection — Hazir Haber Sitesi Scripti 8.2 High2026-03-12
CVE-2019-25511 Jettweb PHP Hazir Haber Sitesi Scripti V3 SQL Injection — Hazir Haber Sitesi Scripti 8.2 High2026-03-12
CVE-2019-25510 Jettweb PHP Hazir Haber Sitesi Scripti V2 Authentication Bypass — Hazir Haber Sitesi Scripti 8.2 High2026-03-12
CVE-2019-25509 XooDigital Lastest Latest SQL Injection via results.php — XooDigital 8.2 High2026-03-12
CVE-2019-25508 Jettweb Php Hazir Ilan Sitesi Scripti V2 SQL Injection via katgetir.php — Hazir Ilan Sitesi Scripti 8.2 High2026-03-12
CVE-2019-25488 Jettweb Hazir Rent A Car Scripti V4 SQL Injection via admin — Rent A Car Scripti 8.2 High2026-03-12
CVE-2019-25482 Jettweb PHP Hazir Rent A Car Sitesi Scripti V2 SQL Injection — Hazir Rent A Car Sitesi Scripti 8.2 High2026-03-12
CVE-2019-25481 iScripts ReserveLogic Lastest SQL Injection via search endpoint — iScripts ReserveLogic 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.