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-3135 fcba_zzm ics-park Smart Park Management System update sql injection — ics-park Smart Park Management System 6.3 Medium 2025-04-03
CVE-2025-3134 code-projects Payroll Management System add_overtime.php sql injection — Payroll Management System 6.3 Medium 2025-04-03
CVE-2025-3120 SourceCodester Apartment Visitors Management System add-apartment.php sql injection — Apartment Visitors Management System 6.3 Medium 2025-04-02
CVE-2025-3119 SourceCodester Online Tutor Portal manage_course.php sql injection — Online Tutor Portal 6.3 Medium 2025-04-02
CVE-2025-3118 SourceCodester Online Tutor Portal view_course.php sql injection — Online Tutor Portal 6.3 Medium 2025-04-02
CVE-2024-12410 Front End Users <= 3.2.32 - Authenticated (Admin+) SQL injection — Front End Users 4.9 Medium 2025-04-02
CVE-2024-36465 SQL injection in Zabbix API — Zabbix 8.8AI High AI 2025-04-02
CVE-2025-31619 WordPress Actionwear products sync plugin <= 2.3.3 - SQL Injection vulnerability — Actionwear products sync 8.5 High 2025-04-01
CVE-2025-31579 WordPress WP AutoKeyword plugin <= 1.0 - SQL Injection vulnerability — WP AutoKeyword 9.3 Critical 2025-04-01
CVE-2025-31553 WordPress Advanced WooCommerce Product Sales Reporting plugin <= 4.1.1 - SQL Injection vulnerability — Advanced WooCommerce Product Sales Reporting 9.3 Critical 2025-04-01
CVE-2025-31561 WordPress Ultimate Push Notifications plugin <= 1.2.0 - SQL Injection vulnerability — Ultimate Push Notifications 8.5 High 2025-04-01
CVE-2025-31564 WordPress Ai Auto Tool Content Writing Assistant (Gemini Writer, ChatGPT ) All in One plugin <= 2.2.6 - SQL Injection vulnerability — Ai Auto Tool Content Writing Assistant (Gemini Writer, ChatGPT ) All in One 8.5 High 2025-04-01
CVE-2025-31534 WordPress Shopper plugin <= 3.2.5 - SQL Injection vulnerability — Shopper 9.3 Critical 2025-04-01
CVE-2025-31551 WordPress Salesmate Add-On for Gravity Forms plugin <= 2.0.3 - SQL Injection vulnerability — Salesmate Add-On for Gravity Forms 9.3 Critical 2025-04-01
CVE-2025-31552 WordPress RSVPMarker plugin <= 11.6.7 - SQL Injection vulnerability — RSVPMarker 9.3 Critical 2025-04-01
CVE-2025-31531 WordPress History Log by click5 plugin <= 1.0.13 - SQL Injection vulnerability — History Log by click5 9.3 Critical 2025-04-01
CVE-2025-31089 WordPress Order Splitter for WooCommerce plugin <= 5.3.0 - SQL Injection Vulnerability — Order Splitter for WooCommerce 8.5 High 2025-04-01
CVE-2025-30807 WordPress Next-Cart Store to WooCommerce Migration plugin <= 3.9.4 - SQL Injection vulnerability — Next-Cart Store to WooCommerce Migration 9.3 Critical 2025-04-01
CVE-2025-3096 Clinics Patient Management System SQL Injection — Clinic's Patient Management System 9.8AI Critical AI 2025-04-01
CVE-2025-31910 WordPress BookingPress plugin <= 1.1.28 - SQL Injection vulnerability — BookingPress 7.6 High 2025-04-01
CVE-2025-31024 WordPress RJ Quickcharts plugin <= 0.6.1 - SQL Injection vulnerability — RJ Quickcharts 8.5 High 2025-04-01
CVE-2025-30971 WordPress XV Random Quotes plugin <= 2.0.0 - SQL Injection vulnerability — XV Random Quotes 9.3 Critical 2025-04-01
CVE-2025-30886 WordPress JS Help Desk plugin <= 2.9.2 - SQL Injection vulnerability — JS Help Desk 9.3 Critical 2025-04-01
CVE-2025-30876 WordPress Ads by WPQuads plugin <= 2.0.87.1 - SQL Injection Vulnerability — Ads by WPQuads 9.3 Critical 2025-04-01
CVE-2025-30622 WordPress PostMash plugin <= 1.0.3 - SQL Injection Vulnerability — PostMash 9.3 Critical 2025-04-01
CVE-2025-30774 WordPress Quiz Maker plugin <= 6.6.8.7 - SQL Injection vulnerability — Quiz Maker 8.2 High 2025-04-01
CVE-2025-30589 WordPress Flickr set slideshows plugin <= 0.9 - SQL Injection Vulnerability — Flickr set slideshows 8.5 High 2025-04-01
CVE-2025-3045 oretnom23/SourceCodester Apartment Visitor Management System remove-apartment.php sql injection — Apartment Visitor Management System 6.3 Medium 2025-04-01
CVE-2025-3039 code-projects Payroll Management System add_employee.php sql injection — Payroll Management System 6.3 Medium 2025-03-31
CVE-2025-3038 code-projects Payroll Management System view_account.php sql injection — Payroll Management System 6.3 Medium 2025-03-31

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