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-10062 itsourcecode Student Information Management System login.php sql injection — Student Information Management System 7.3 High 2025-09-06
CVE-2025-10033 itsourcecode Online Discussion Forum admin sql injection — Online Discussion Forum 7.3 High 2025-09-06
CVE-2025-10031 Campcodes Grocery Sales and Inventory System ajax.php sql injection — Grocery Sales and Inventory System 7.3 High 2025-09-06
CVE-2025-10030 Campcodes Grocery Sales and Inventory System ajax.php sql injection — Grocery Sales and Inventory System 7.3 High 2025-09-06
CVE-2025-10046 ELEX WooCommerce Google Shopping (Google Product Feed) <= 1.4.3 - Authenticated (Admin+) SQL Inejction — ELEX WooCommerce Google Shopping (Google Product Feed) 4.9 Medium 2025-09-06
CVE-2025-10003 UsersWP – Front-end login form, User Registration, User Profile & Members Directory plugin for WP <= 1.2.44 - Authenticated (Subscriber+) SQL Injection — UsersWP – Front-end login form, User Registration, User Profile & Members Directory plugin for WP 6.5 Medium 2025-09-06
CVE-2025-9085 User Registration & Membership <= 4.3.0 - Authenticated (Admin+) SQL Injection — User Registration & Membership – Free & Paid Memberships, Subscriptions, Content Restriction, User Profile, Custom User Registration & Login Builder 4.9 Medium 2025-09-06
CVE-2025-58439 ERP: Possibility of SQL injection due to missing validation — erpnext 8.1 High 2025-09-06
CVE-2025-10025 PHPGurukul Online Course Registration semester.php sql injection — Online Course Registration 7.3 High 2025-09-05
CVE-2025-58628 WordPress Miraculous Theme < 2.0.9 - SQL Injection Vulnerability — Miraculous 9.3 Critical 2025-09-05
CVE-2025-10012 Portabilis i-Educar educar_historico_escolar_lst.php sql injection — i-Educar 6.3 Medium 2025-09-05
CVE-2025-10011 Portabilis i-Educar edit sql injection — i-Educar 6.3 Medium 2025-09-05
CVE-2025-58881 WordPress New Simple Gallery Plugin <= 8.0 - SQL Injection Vulnerability — New Simple Gallery 8.5 High 2025-09-05
CVE-2025-58789 WordPress WP Full Stripe Free Plugin <= 8.2.5 - SQL Injection Vulnerability — WP Full Stripe Free 7.6 High 2025-09-05
CVE-2025-58788 WordPress License Manager for WooCommerce Plugin <= 3.0.12 - SQL Injection Vulnerability — License Manager for WooCommerce 7.6 High 2025-09-05
CVE-2025-58780 ScienceLogic SL1 SQL注入漏洞 — SL1 7.2 High 2025-09-05
CVE-2025-8311 DotCMS 安全漏洞 — dotCMS Cloud Services (dCS) 8.8AI High AI 2025-09-04
CVE-2025-7385 SQL Injection in GOV CMS — GOV CMS 9.8AI Critical AI 2025-09-04
CVE-2025-41034 SQL injection vulnerability in appRain CMF — appRain CMF 9.8 - 2025-09-04
CVE-2025-41033 SQL injection vulnerability in appRain CMF — appRain CMF 9.8 - 2025-09-04
CVE-2025-41032 SQL injection vulnerability in appRain CMF — appRain CMF 8.8 - 2025-09-04
CVE-2025-9933 PHPGurukul Beauty Parlour Management System view-appointment.php sql injection — Beauty Parlour Management System 7.3 High 2025-09-03
CVE-2025-9932 PHPGurukul Beauty Parlour Management System update-image.php sql injection — Beauty Parlour Management System 7.3 High 2025-09-03
CVE-2025-9930 1000projects Beauty Parlour Management System contact-us.php sql injection — Beauty Parlour Management System 7.3 High 2025-09-03
CVE-2025-9928 projectworlds Travel Management System viewcategory.php sql injection — Travel Management System 7.3 High 2025-09-03
CVE-2025-9927 projectworlds Travel Management System viewpackage.php sql injection — Travel Management System 7.3 High 2025-09-03
CVE-2025-9926 projectworlds Travel Management System viewsubcategory.php sql injection — Travel Management System 7.3 High 2025-09-03
CVE-2025-9925 projectworlds Travel Management System detail.php sql injection — Travel Management System 7.3 High 2025-09-03
CVE-2025-9924 projectworlds Travel Management System enquiry.php sql injection — Travel Management System 7.3 High 2025-09-03
CVE-2025-9919 1000projects Beauty Parlour Management System bwdates-reports-details.php sql injection — Beauty Parlour Management System 7.3 High 2025-09-03

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