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

Goal: 1000 CNY · Raised: 1336 CNY

100%

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

10236 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-2026-15537 SourceCodester Online Book Store System login.php sql injection — Online Book Store System 7.3 High 2026-07-13
CVE-2026-15536 itsourcecode Hospital Management System patviewprescription.php sql injection — Hospital Management System 6.3 Medium 2026-07-13
CVE-2026-15523 CodeAstro Simple Online Leave Management System dashboard.php sql injection — Simple Online Leave Management System 6.3 Medium 2026-07-13
CVE-2026-15517 Jinher OA PlanGiveOut.aspx sql injection — OA 7.3 High 2026-07-13
CVE-2026-15514 Metasoft 美特软件 MetaCRM PHPRPC Remote Call rpc.jsp RPCService.query sql injection — MetaCRM 7.3 High 2026-07-12
CVE-2026-15502 AojiaoZero Antaris PayPal IPN Payment ipn.php _rewardPurchase sql injection — Antaris 6.3 Medium 2026-07-12
CVE-2026-56281 Capgo - SQL Injection via Unvalidated limit Parameter in Admin Stats Endpoint — Capgo 3.8 Low 2026-07-12
CVE-2026-15498 sergomanov SmartHomeAdatum Login users.php sql injection — SmartHomeAdatum 7.3 High 2026-07-12
CVE-2026-15494 AMTT Hotel Broadband Operation System switch_status.php sql injection — Hotel Broadband Operation System 4.7 Medium 2026-07-12
CVE-2026-15490 RafyMrX TOKO-ONLINE-ROTI add.php sql injection — TOKO-ONLINE-ROTI 7.3 High 2026-07-12
CVE-2026-15489 RafyMrX TOKO-ONLINE-ROTI login.php sql injection — TOKO-ONLINE-ROTI 7.3 High 2026-07-12
CVE-2026-15482 Aster Telecom Azcall HTTP sis.php sql injection — Azcall 7.3 High 2026-07-12
CVE-2026-15478 IceHRM UserReport Endpoint EmployeeAttendanceReport.php sql injection — IceHRM 6.3 Medium 2026-07-12
CVE-2026-15477 Bahmni bahmnicore Search Endpoint sql additionalParams sql injection — bahmnicore 6.3 Medium 2026-07-12
CVE-2026-60090 PraisonAI before 4.6.78 SQL/CQL Injection via vector dimension — PraisonAI 9.8 Critical 2026-07-11
CVE-2026-4661 WP CTA <= 2.2.2 - Unauthenticated Time-Based Blind SQL Injection via 'fildname' Parameter — WP CTA – Call Now Button, Sticky Button & Call to Action Builder 7.5 High 2026-07-11
CVE-2025-5017 Catalyst Connect Zoho CRM Client Portal <= 2.2.0 - Authenticated (Administrator+) SQL Injection via uid Parameter — Catalyst Connect Zoho CRM Client Portal 4.9 Medium 2026-07-11
CVE-2026-15335 Booking Package <= 1.7.20 - Unauthenticated SQL Injection via 'email' Form Parameter — Booking Package 7.5 High 2026-07-11
CVE-2026-15072 KiviCare <= 4.5.0 - Authenticated (Doctor+) SQL Injection via 'orderby' Parameter in KCQueryBuilder — KiviCare – Clinic & Patient Management System (EHR) 6.5 Medium 2026-07-11
CVE-2026-13262 Majestic Support <= 1.1.9 - Authenticated (Subscriber+) SQL Injection via 'val' Parameter — Majestic Support – The Leading-Edge Help Desk & Customer Support Plugin 6.5 Medium 2026-07-11
CVE-2026-15073 KiviCare <= 4.5.0 - Authenticated (Doctor+) SQL Injection via 'orderby' Parameter in DoctorSessionController — KiviCare – Clinic & Patient Management System (EHR) 6.5 Medium 2026-07-11
CVE-2026-15081 Location Selector - Critical - SQL Injection - SA-CONTRIB-2026-072 — Location Selector - - 2026-07-10
CVE-2026-13242 Geolocation Field - Critical - SQL Injection - SA-CONTRIB-2026-062 — Geolocation Field - - 2026-07-10
CVE-2026-47199 Frappe: check_safe_sql_query Permits SELECT INTO OUTFILE — frappe - - 2026-07-10
CVE-2026-57230 OpenReplay: Authenticated ClickHouse SQL injection via session search — openreplay 5.4 Medium 2026-07-10
CVE-2026-55405 LangChain4j: SQL injection via metadata filters in langchain4j-mariadb and langchain4j-pgvector — langchain4j 7.6 High 2026-07-10
CVE-2026-11321 GLPI DataInjection Plugin Authenticated SQL Injection via CSV Import — datainjection 6.4 Medium 2026-07-10
CVE-2026-61461 Dify < 1.16.0-rc1 SQL Injection via MyScale Vector Store search_by_full_text — dify 8.8 High 2026-07-10
CVE-2026-5801 SQLi in Semtek Informatics' SEM-PMP — SEM-PMP 9.8 Critical 2026-07-10
CVE-2026-53448 Coturn: SQL Injection in HTTPS Admin Panel Delete Operations — coturn 7.2 High 2026-07-10

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