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-2019-25459 Web Ofisi Emlak V2 SQL Injection via emlak-ara.html — Emlak 9.8 Critical 2026-02-22
CVE-2019-25458 Web Ofisi Firma Rehberi v1 SQL Injection via firmalar.html — Firma Rehberi 9.8 Critical 2026-02-22
CVE-2019-25457 Web Ofisi Firma v13 SQL Injection via oz Parameter — Firma 7.5 High 2026-02-22
CVE-2019-25455 Web Ofisi E-Ticaret v3 SQL Injection via ara.html — Ticaret 7.5 High 2026-02-22
CVE-2019-25456 Web Ofisi Emlak v2 SQL Injection via ara Parameter — Emlak 9.1 Critical 2026-02-22
CVE-2019-25391 Ashop Shopping Cart Software Lastest Latest SQL Injection via bannedcustomers.php — Ashop Shopping Cart Software 8.2 High 2026-02-22
CVE-2019-25366 microASP Portal+ CMS SQL Injection via pagina.phtml — microASP (Portal+) CMS 8.2 High 2026-02-22
CVE-2019-25440 WebIncorp ERP Every version SQL Injection via product_detail.php — WebIncorp ERP 8.2 High 2026-02-22
CVE-2019-25439 NoviSmart CMS SQL Injection via Referer HTTP Header — NoviSmart CMS 8.2 High 2026-02-22
CVE-2019-25433 XOOPS CMS 2.5.9 SQL Injection via gerar_pdf.php — XOOPS CMS 8.2 High 2026-02-22
CVE-2019-25452 Dolibarr ERP/CRM 10.0.1 SQL Injection via elemid — Dolibarr ERP/CRM 7.5 High 2026-02-22
CVE-2019-25450 Dolibarr ERP/CRM 10.0.1 SQL Injection via card.php — Dolibarr ERP/CRM 7.5 High 2026-02-22
CVE-2019-25446 DIGIT CENTRIS ERP Every version SQL Injection via datum1 Parameter — DIGIT CENTRIS 8.2 High 2026-02-22
CVE-2019-25443 Inventory Webapp SQL Injection via add-item.php — inventory-webapp 8.2 High 2026-02-22
CVE-2019-25442 Web Wiz Forums 12.01 SQL Injection via PF Parameter — Web Wiz Forums 7.5 High 2026-02-22
CVE-2026-2912 code-projects Online Reviewer System studentresult-view.php sql injection — Online Reviewer System 7.3 High 2026-02-22
CVE-2026-2867 itsourcecode Vehicle Management System billaction.php sql injection — Vehicle Management System 7.3 High 2026-02-21
CVE-2026-27470 ZoneMinder: Second-Order SQL Injection in `getNearEvents()` via Stored Event Name and Cause Fields — zoneminder 8.8 High 2026-02-21
CVE-2026-2865 itsourcecode Agri-Trading Online Shopping System HTTP POST Request productcontroller.php sql injection — Agri-Trading Online Shopping System 7.3 High 2026-02-21
CVE-2019-25438 LabCollector 5.423 SQL Injection via login.php — LabCollector 7.5 High 2026-02-20
CVE-2019-25432 Part-DB 0.4 Authentication Bypass via login.php — Part-DB 7.5 High 2026-02-20
CVE-2019-25431 delpino73 Blue-Smiley-Organizer 1.32 SQL Injection via datetime — Blue-Smiley-Organizer 8.2 High 2026-02-20
CVE-2019-25444 Fiverr Clone Script 1.2.2 SQL Injection via page Parameter — Fiverr Clone Script 9.1 Critical 2026-02-20
CVE-2026-2848 SourceCodester Simple Responsive Tourism Website Registration Master.php sql injection — Simple Responsive Tourism Website 7.3 High 2026-02-20
CVE-2026-24956 WordPress Download Manager Addons for Elementor plugin <= 1.3.0 - SQL Injection vulnerability — Download Manager Addons for Elementor 9.3 Critical 2026-02-20
CVE-2026-24959 WordPress JS Help Desk plugin <= 3.0.1 - SQL Injection vulnerability — JS Help Desk 8.5 High 2026-02-20
CVE-2025-69366 WordPress Emerce Core plugin <= 1.8 - SQL Injection vulnerability — Emerce Core 9.3 Critical 2026-02-20
CVE-2025-69337 WordPress Wolmart Core plugin <= 1.9.6 - SQL Injection vulnerability — Wolmart Core 9.3 Critical 2026-02-20
CVE-2025-69365 WordPress Uroan Core plugin <= 1.4.4 - SQL Injection vulnerability — Uroan Core 9.3 Critical 2026-02-20
CVE-2025-69310 WordPress Woodly Core plugin <= 1.4 - SQL Injection vulnerability — Woodly Core 9.3 Critical 2026-02-20

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