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-5856 PHPGurukul BP Monitoring Management System registration.php sql injection — BP Monitoring Management System 7.3 High 2025-06-09
CVE-2025-5838 PHPGurukul Employee Record Management System adminprofile.php sql injection — Employee Record Management System 6.3 Medium 2025-06-07
CVE-2025-5837 PHPGurukul Employee Record Management System allemployees.php sql injection — Employee Record Management System 6.3 Medium 2025-06-07
CVE-2025-5784 PHPGurukul Employee Record Management System myexp.php sql injection — Employee Record Management System 6.3 Medium 2025-06-06
CVE-2025-29892 Qsync Central — Qsync Central 8.8AI High AI 2025-06-06
CVE-2025-5783 PHPGurukul Employee Record Management System editmyexp.php sql injection — Employee Record Management System 6.3 Medium 2025-06-06
CVE-2025-5782 PHPGurukul Employee Record Management System resetpassword.php sql injection — Employee Record Management System 6.3 Medium 2025-06-06
CVE-2025-5780 code-projects Patient Record Management System view_dental.php sql injection — Patient Record Management System 6.3 Medium 2025-06-06
CVE-2025-5779 code-projects Patient Record Management System birthing.php sql injection — Patient Record Management System 6.3 Medium 2025-06-06
CVE-2025-5778 1000 Projects ABC Courier Management System admin sql injection — ABC Courier Management System 7.3 High 2025-06-06
CVE-2025-49421 WordPress WP Text Expander plugin <= 1.0.1 - SQL Injection Vulnerability — WP Text Expander 7.6 High 2025-06-06
CVE-2023-26003 WordPress WP Post Corrector <= 1.0.2 - SQL Injection Vulnerability — WP Post Corrector 7.6 High 2025-06-06
CVE-2025-26590 WordPress Complete Google Seo Scan plugin <= 3.5.1 - SQL Injection Vulnerability — Complete Google Seo Scan 7.6 High 2025-06-06
CVE-2025-30989 WordPress Libro de Reclamaciones y Quejas plugin <= 0.9 - SQL Injection Vulnerability — Libro de Reclamaciones y Quejas 7.6 High 2025-06-06
CVE-2025-49328 WordPress Store Locator WordPress plugin <= 1.5.1 - SQL Injection Vulnerability — Store Locator WordPress 7.6 High 2025-06-06
CVE-2025-49327 WordPress ShortLinks Pro plugin <= 1.0.7 - SQL Injection Vulnerability — ShortLinks Pro 7.6 High 2025-06-06
CVE-2025-49326 WordPress GamiPress plugin <= 7.4.5 - SQL Injection Vulnerability — GamiPress 7.6 High 2025-06-06
CVE-2025-49323 WordPress Hydra Booking plugin <= 1.1.10 - SQL Injection Vulnerability — Hydra Booking 8.5 High 2025-06-06
CVE-2025-49315 WordPress Persian Woocommerce SMS plugin <= 7.0.10 - SQL Injection Vulnerability — Persian Woocommerce SMS 7.6 High 2025-06-06
CVE-2025-49263 WordPress WC Vendors Marketplace plugin <= 2.5.6 - SQL Injection Vulnerability — WC Vendors Marketplace 7.6 High 2025-06-06
CVE-2025-5762 code-projects Patient Record Management System view_hematology.php sql injection — Patient Record Management System 6.3 Medium 2025-06-06
CVE-2025-5761 PHPGurukul BP Monitoring Management System edit-family-member.php sql injection — BP Monitoring Management System 6.3 Medium 2025-06-06
CVE-2025-5759 PHPGurukul Local Services Search Engine Management System edit-person-detail.php sql injection — Local Services Search Engine Management System 7.3 High 2025-06-06
CVE-2025-5758 SourceCodester Open Source Clinic Management System doctor.php sql injection — Open Source Clinic Management System 7.3 High 2025-06-06
CVE-2025-5756 code-projects Real Estate Property Management System EditCity.php sql injection — Real Estate Property Management System 7.3 High 2025-06-06
CVE-2025-5755 SourceCodester Open Source Clinic Management System email_config.php sql injection — Open Source Clinic Management System 7.3 High 2025-06-06
CVE-2025-5729 code-projects Health Center Patient Record Management System birthing_record.php sql injection — Health Center Patient Record Management System 6.3 Medium 2025-06-06
CVE-2025-5563 WP-Addpub <= 1.2.8 - Authenticated (Contributor+) SQL Injection — WP-Addpub 6.5 Medium 2025-06-06
CVE-2025-4964 WP Online Users Stats <= 1.0.0 - Authenticated (Editor+) SQL Injection via table_name Parameter — WP Online Users Stats 4.9 Medium 2025-06-06
CVE-2025-5716 SourceCodester Open Source Clinic Management System login.php sql injection — Open Source Clinic Management System 7.3 High 2025-06-06

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