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

Goal: 1000 CNY · Raised: 1336 CNY

100%

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

10280 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-14215 code-projects Currency Exchange System edit.php sql injection — Currency Exchange System 7.3 High 2025-12-08
CVE-2025-14214 itsourcecode Student Information System section_edit1.php sql injection — Student Information System 6.3 Medium 2025-12-08
CVE-2025-14212 projectworlds Advanced Library Management System member_search.php sql injection — Advanced Library Management System 7.3 High 2025-12-08
CVE-2025-14211 projectworlds Advanced Library Management System delete_book.php sql injection — Advanced Library Management System 7.3 High 2025-12-08
CVE-2025-14210 projectworlds Advanced Library Management System delete_member.php sql injection — Advanced Library Management System 7.3 High 2025-12-08
CVE-2025-14209 Campcodes School File Management System update_query.php sql injection — School File Management System 7.3 High 2025-12-08
CVE-2025-14207 tushar-2223 Hotel-Management-System invoiceprint.php sql injection — Hotel-Management-System 7.3 High 2025-12-08
CVE-2025-14203 code-projects Question Paper Generator selectquestionuser.php sql injection — Question Paper Generator 6.3 Medium 2025-12-07
CVE-2025-14193 code-projects Employee Profile Management System view_personnel.php sql injection — Employee Profile Management System 6.3 Medium 2025-12-07
CVE-2025-14192 RashminDungrani online-banking auth_login.php sql injection — online-banking 7.3 High 2025-12-07
CVE-2025-14190 Chanjet TPlus sql injection — TPlus 7.3 High 2025-12-07
CVE-2025-14189 Chanjet CRM jxf_dump_table_demo.php sql injection — CRM 7.3 High 2025-12-07
CVE-2025-14185 Yonyou U8 Cloud AppServletService.class sql injection — U8 Cloud 6.3 Medium 2025-12-07
CVE-2025-13922 Tag, Category, and Taxonomy Manager – AI Autotagger with OpenAI <= 3.40.1 - Authenticated (Contributor+) SQL Injection via ORDER BY Clause — Tag, Category, and Taxonomy Manager – AI Autotagger with OpenAI 6.5 Medium 2025-12-06
CVE-2025-14091 TrippWasTaken PHP-Guitar-Shop Product Details product.php sql injection — PHP-Guitar-Shop 7.3 High 2025-12-05
CVE-2025-14090 AMTT Hotel Broadband Operation System cardmake_down.php sql injection — Hotel Broadband Operation System 4.7 Medium 2025-12-05
CVE-2025-12850 My auctions allegro <= 3.6.32 - Unauthenticated SQL Injection via auction_id — My auctions allegro 7.5 High 2025-12-05
CVE-2025-13373 Advantech iView SQL Injection — iView 7.5 High 2025-12-04
CVE-2024-58276 Obi08-Enrollment System 1.0 login.php SQL Injection — Obi08/Enrollment System 8.7 High 2025-12-04
CVE-2023-53734 dawa-pharma-1.0 - SQL Injection via Email Parameter — dawa-pharma 9.8AI Critical AI 2025-12-04
CVE-2025-14012 JIZHICMS Batch Delete Comments deleteAll.html delete sql injection — JIZHICMS 4.7 Medium 2025-12-04
CVE-2025-14011 JIZHICMS Add Display Name Field addcomment.html commentlist sql injection — JIZHICMS 4.7 Medium 2025-12-04
CVE-2025-62173 Authenticated SQL Injection in Endpoint Module Rest API — restapps 8.8AI High AI 2025-12-03
CVE-2025-13359 Tag, Category, and Taxonomy Manager – AI Autotagger with OpenAI <= 3.40.1 - Authenticated (Contributor+) SQL Injection — Tag, Category, and Taxonomy Manager – AI Autotagger with OpenAI 6.5 Medium 2025-12-03
CVE-2025-13495 FluentCart A New Era of eCommerce <= 1.3.1 - Authenticated (Administrator+) SQL Injection via 'groupKey' Parameter — FluentCart A New Era of eCommerce – Faster, Lighter, and Simpler 4.9 Medium 2025-12-03
CVE-2025-13372 Potential SQL injection in FilteredRelation column aliases on PostgreSQL — Django 9.8AI Critical AI 2025-12-02
CVE-2025-41013 SQL injection vulnerability in TCMAN GIM — GIM 9.8AI Critical AI 2025-12-02
CVE-2025-12465 Blind SQL Injection in QuickCMS — QuickCMS 7.2AI High AI 2025-12-02
CVE-2025-13090 WP Directory Kit <= 1.4.6 - Authenticated (Admin+) SQL Injection — WP Directory Kit 4.9 Medium 2025-12-02
CVE-2025-13724 VikRentCar Car Rental Management System <= 1.4.4 - Authenticated (Author+) SQL Injection via 'month' Parameter — VikRentCar Car Rental Management System 7.5 High 2025-12-02

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