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

Goal: 1000 CNY · Raised: 1336 CNY

100%

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

10269 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-1183 CodeZips Gym Management System more-userprofile.php sql injection — Gym Management System 6.3 Medium 2025-02-12
CVE-2025-26520 Cacti 安全漏洞 — Cacti 7.6 High 2025-02-12
CVE-2025-1173 1000 Projects Bookstore Management System process_users_del.php sql injection — Bookstore Management System 4.7 Medium 2025-02-11
CVE-2025-1172 1000 Projects Bookstore Management System addtocart.php sql injection — Bookstore Management System 6.3 Medium 2025-02-11
CVE-2025-1168 SourceCodester Contact Manager with Export to VCF delete-contact.php sql injection — Contact Manager with Export to VCF 6.3 Medium 2025-02-11
CVE-2025-1167 Mayuri K Employee Management System Update_User.php sql injection — Employee Management System 6.3 Medium 2025-02-11
CVE-2025-1162 code-projects Job Recruitment load\_user-profile.php sql injection — Job Recruitment 6.3 Medium 2025-02-10
CVE-2025-1158 ESAFENET CDG addPolicyToSafetyGroup.jsp sql injection — CDG 6.3 Medium 2025-02-10
CVE-2025-1157 Allims lab.online model_recuperar_senha.php sql injection — lab.online 6.3 Medium 2025-02-10
CVE-2025-1156 Pix Software Vivaz servlet sql injection — Vivaz 7.3 High 2025-02-10
CVE-2025-1154 xxyopen Novel books sql injection — Novel 6.3 Medium 2025-02-10
CVE-2024-13440 Super Store Finder <= 7.0 - Unauthenticated SQL Injection to Stored Cross-Site Scripting — Super Store Finder 8.2 High 2025-02-09
CVE-2025-1117 CoinRemitter sql injection — CoinRemitter 7.3 High 2025-02-08
CVE-2025-1116 Dreamvention Live AJAX Search Free live_search.searchresults search sql injection — Live AJAX Search Free 7.3 High 2025-02-08
CVE-2025-25151 WordPress uListing Plugin <= 2.1.6 - SQL Injection vulnerability — uListing 8.5 High 2025-02-07
CVE-2025-25116 WordPress Link to URL / Post plugin <=1.3 - SQL Injection vulnerability — Link to URL / Post 7.6 High 2025-02-07
CVE-2025-22699 WordPress Traveler Code plugin < 3.1.2 - Unauthenticated Arbitrary SQL Execution vulnerability — Traveler Code 9.0 Critical 2025-02-04
CVE-2025-22700 WordPress Traveler Code plugin < 3.1.3 - Subscriber+ Arbitrary SQL Execution vulnerability — Traveler Code 8.5 High 2025-02-04
CVE-2025-22206 Extension - joomsky.com - SQL injection in JS jobs component version 1.1.5 - 1.4.2 for Joomla — JS Jobs component for Joomla 7.2 - 2025-02-04
CVE-2025-24901 SQL Injection endpoint 'deletar_permissao.php' parameter 'c', 'a', 'r' in WeGIA — WeGIA 8.8 - 2025-02-03
CVE-2025-24902 SQL Injection endpoint 'salvar_cargo.php' parameter 'id_cargo' in WeGIA — WeGIA 8.8 - 2025-02-03
CVE-2025-24905 SQL Injection endpoint 'get_codigobarras_cobranca.php' parameter 'codigo' in WeGIA — WeGIA 8.8 - 2025-02-03
CVE-2025-24906 SQL Injection endpoint 'get_detalhes_cobranca.php' parameter 'codigo' in WeGIA — WeGIA 8.8 - 2025-02-03
CVE-2025-24957 SQL Injection endpoint 'get_detalhes_socio.php' parameter 'id_socio' in WeGIA — WeGIA 8.8 - 2025-02-03
CVE-2025-24958 SQL Injection endpoint 'salvar_tag.php' parameter 'id_tag' in WeGIA — WeGIA 8.8 - 2025-02-03
CVE-2025-22691 WordPress WP Travel plugin <= 10.1.3 - SQL Injection vulnerability — WP Travel 7.6 High 2025-02-03
CVE-2025-22693 WordPress Contest Gallery plugin <= 25.1.0 - SQL Injection vulnerability — Contest Gallery 7.6 High 2025-02-03
CVE-2025-25181 Advantive VeraCore 安全漏洞 — VeraCore 5.8 Medium 2025-02-03
CVE-2025-0967 code-projects Chat System add_chatroom.php sql injection — Chat System 6.3 Medium 2025-02-02
CVE-2025-0950 itsourcecode Tailoring Management System staffview.php sql injection — Tailoring Management System 6.3 Medium 2025-02-01

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