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

Goal: 1000 CNY · Raised: 1336 CNY

100%

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

10283 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-5579 PHPGurukul Dairy Farm Shop Management System search-product.php sql injection — Dairy Farm Shop Management System 7.3 High 2025-06-04
CVE-2025-5578 PHPGurukul Dairy Farm Shop Management System sales-report-details.php sql injection — Dairy Farm Shop Management System 7.3 High 2025-06-04
CVE-2025-5577 PHPGurukul Dairy Farm Shop Management System profile.php sql injection — Dairy Farm Shop Management System 7.3 High 2025-06-04
CVE-2025-5576 PHPGurukul Dairy Farm Shop Management System bwdate-report-details.php sql injection — Dairy Farm Shop Management System 7.3 High 2025-06-04
CVE-2025-5575 PHPGurukul Dairy Farm Shop Management System add-product.php sql injection — Dairy Farm Shop Management System 7.3 High 2025-06-04
CVE-2025-5574 PHPGurukul Dairy Farm Shop Management System add-company.php sql injection — Dairy Farm Shop Management System 7.3 High 2025-06-04
CVE-2025-5569 IdeaCMS getList.html Goods sql injection — IdeaCMS 6.3 Medium 2025-06-04
CVE-2025-5566 PHPGurukul Notice Board System search-notice.php sql injection — Notice Board System 6.3 Medium 2025-06-04
CVE-2025-5562 PHPGurukul Curfew e-Pass Management System edit-category-detail.php sql injection — Curfew e-Pass Management System 7.3 High 2025-06-04
CVE-2025-5561 PHPGurukul Curfew e-Pass Management System view-pass-detail.php sql injection — Curfew e-Pass Management System 7.3 High 2025-06-04
CVE-2025-5560 PHPGurukul Curfew e-Pass Management System index.php sql injection — Curfew e-Pass Management System 7.3 High 2025-06-04
CVE-2025-5558 PHPGurukul Teacher Subject Allocation Management System changeimage.php sql injection — Teacher Subject Allocation Management System 6.3 Medium 2025-06-04
CVE-2025-5557 PHPGurukul Teacher Subject Allocation Management System edit-course.php sql injection — Teacher Subject Allocation Management System 6.3 Medium 2025-06-04
CVE-2025-5556 PHPGurukul Teacher Subject Allocation Management System edit-teacher-info.php sql injection — Teacher Subject Allocation Management System 6.3 Medium 2025-06-04
CVE-2025-5554 PHPGurukul Rail Pass Management System pass-bwdates-reports-details.php sql injection — Rail Pass Management System 6.3 Medium 2025-06-04
CVE-2025-5553 PHPGurukul Rail Pass Management System download-pass.php sql injection — Rail Pass Management System 7.3 High 2025-06-04
CVE-2025-5546 PHPGurukul Daily Expense Tracker System expense-reports-detailed.php sql injection — Daily Expense Tracker System 6.3 Medium 2025-06-03
CVE-2025-48998 Dataease MYSQL JDBC File Reading Vulnerability — dataease 8.8AI High AI 2025-06-03
CVE-2025-5493 Baison Channel Middleware Product ToJsonByControlName sql injection — Channel Middleware Product 6.3 Medium 2025-06-03
CVE-2025-5103 Ultimate Gift Cards for WooCommerce <= 3.1.4 - Authenticated (Administrator+) SQL Injection via wps_wgm_save_post Function — Ultimate Gift Cards for WooCommerce 4.9 Medium 2025-06-03
CVE-2025-1750 SQL Injection in run-llama/llama_index — run-llama/llama_index 9.8AI Critical AI 2025-06-02
CVE-2025-5435 Marwal Infotech CMS page.php sql injection — CMS 7.3 High 2025-06-02
CVE-2025-5434 Aem Solutions CMS page.php sql injection — CMS 7.3 High 2025-06-02
CVE-2025-5433 Fengoffice Feng Office index.php sql injection — Feng Office 6.3 Medium 2025-06-02
CVE-2025-5432 AssamLook CMS view_tender.php sql injection — CMS 6.3 Medium 2025-06-02
CVE-2025-5431 AssamLook CMS department-profile.php sql injection — CMS 6.3 Medium 2025-06-02
CVE-2025-5430 AssamLook CMS product.php sql injection — CMS 6.3 Medium 2025-06-02
CVE-2025-5403 chaitak-gorai Blogbook GET Parameter view_all_posts.php sql injection — Blogbook 6.3 Medium 2025-06-01
CVE-2025-5402 chaitak-gorai Blogbook GET Parameter edit_post.php sql injection — Blogbook 7.3 High 2025-06-01
CVE-2025-5401 chaitak-gorai Blogbook GET Parameter post.php sql injection — Blogbook 7.3 High 2025-06-01

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