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

Goal: 1000 CNY · Raised: 1336 CNY

100%

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

10247 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-2024-9808 SourceCodester Online Eyewear Shop sql injection — Online Eyewear Shop 6.3 Medium 2024-10-10
CVE-2024-9804 code-projects Blood Bank System campsdetails.php sql injection — Blood Bank System 4.7 Medium 2024-10-10
CVE-2024-9797 code-projects Blood Bank System register.php sql injection — Blood Bank System 7.3 High 2024-10-10
CVE-2024-9790 LyLme_spage sou.php sql injection — LyLme_spage 4.7 Medium 2024-10-10
CVE-2024-9789 LyLme_spage apply.php sql injection — LyLme_spage 4.7 Medium 2024-10-10
CVE-2024-9788 LyLme_spage tag.php sql injection — LyLme_spage 4.7 Medium 2024-10-10
CVE-2024-4658 SQLi in TE Informatics' Nova CMS — Nova CMS 9.8AI Critical AI 2024-10-10
CVE-2024-9201 SQL injection vulnerability in SEUR plugin — SEUR plugin 9.4 Critical 2024-10-10
CVE-2024-9022 TS Poll – Survey, Versus Poll, Image Poll, Video Poll <= 2.4.0 - Authenticated (Administrator+) SQL Injection via orderby Parameter — TS Poll – Survey, Versus Poll, Image Poll, Video Poll 7.2 High 2024-10-10
CVE-2024-9465 Expedition: SQL Injection Leads to Firewall Admin Credential Disclosure — Expedition 9.1AI Critical AI 2024-10-09
CVE-2024-9286 SQLi in TRtek Software's Distant Education Platform — Distant Education Platform 9.8AI Critical AI 2024-10-09
CVE-2024-47334 WordPress Zoho Flow for WordPress plugin <= 2.7.1 - SQL Injection vulnerability — Zoho Flow 7.6 High 2024-10-09
CVE-2024-43468 Microsoft Configuration Manager Remote Code Execution Vulnerability — Microsoft Configuration Manager 9.8 Critical 2024-10-08
CVE-2024-9379 Ivanti CSA 安全漏洞 — CSA (Cloud Services Appliance) 6.5 Medium 2024-10-08
CVE-2024-8911 LatePoint <= 5.0.11 - Unauthenticated Arbitrary User Password Change via SQL Injection — LatePoint Plugin 9.8 Critical 2024-10-08
CVE-2024-9574 SQL Injection vulnerability in SOPlanning — SOPlanning 9.8 Critical 2024-10-07
CVE-2024-9573 SQL Injection vulnerability in SOPlanning — SOPlanning 6.3 Medium 2024-10-07
CVE-2024-47335 WordPress Bit Form plugin <= 2.13.11 - SQL Injection vulnerability — Bit Form 7.6 High 2024-10-07
CVE-2024-9560 ESAFENET CDG Catelogs;logindojojs delCatelogs sql injection — CDG 6.3 Medium 2024-10-06
CVE-2024-47338 WordPress WPExperts Square For GiveWP plugin <= 1.3 - SQL Injection vulnerability — WPExperts Square For GiveWP 8.5 High 2024-10-06
CVE-2024-47350 WordPress YITH WooCommerce Ajax Search plugin <= 2.8.0 - SQL Injection vulnerability — YITH WooCommerce Ajax Search 9.3 Critical 2024-10-06
CVE-2024-45249 Cavok – CWE-89: Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') — Cavok 9.8 Critical 2024-10-06
CVE-2024-9536 ESAFENET CDG MultiServerBackService sql injection — CDG 6.3 Medium 2024-10-05
CVE-2024-47849 Backticks can allow the usage of not-allowed SQL functions — Mediawiki - Cargo 9.8 - 2024-10-05
CVE-2024-7801 SQL injection in get_chart_data in TimeProvider 4100 — TimeProvider 4100 9.8 - 2024-10-04
CVE-2024-42417 Delta Electronics DIAEnergie SQL Injection — DIAEnergie 8.8 High 2024-10-03
CVE-2024-43699 Delta Electronics DIAEnergie SQL Injection — DIAEnergie 9.8 Critical 2024-10-03
CVE-2024-9460 Codezips Online Shopping Portal index.php sql injection — Online Shopping Portal 7.3 High 2024-10-03
CVE-2024-9429 code-projects Restaurant Reservation System filter2.php sql injection — Restaurant Reservation System 6.3 Medium 2024-10-02
CVE-2024-9018 WP Easy Gallery <= 4.8.5 - Authenticated (Contributor+) SQL Injection via key Parameter — WP Easy Gallery – WordPress Gallery Plugin 8.8 High 2024-10-01

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