Skip to content

appsmith has SQL Injection in FilterDataService via Unsafe DROP TABLE Execution

High severity GitHub Reviewed Published Apr 22, 2026 in appsmithorg/appsmith

Package

maven com.appsmith:interfaces (Maven)

Affected versions

<= 1.98

Patched versions

1.99

Description

Summary

A SQL injection vulnerability exists in FilterDataServiceCE.java where the dropTable method constructs a SQL DROP TABLE statement using string concatenation with the table name. If the table name is derived from user input, this allows for arbitrary SQL command execution.

Details

The vulnerability is located in app/server/appsmith-interfaces/src/main/java/com/appsmith/external/services/ce/FilterDataServiceCE.java.

Line 627 in dropTable method:

public void dropTable(String tableName) {
    String dropTableQuery = "DROP TABLE " + tableName + ";";
    executeDbQuery(dropTableQuery);
}

The tableName argument is concatenated directly into the SQL string without validation or escaping.

PoC

If dropTable is exposed to user input (e.g., via a utility API that accepts a table name to clean up), an attacker could provide a value like:
valid_table; DROP TABLE users; --

The resulting query would be:
DROP TABLE valid_table; DROP TABLE users; --;

This would delete the intended table and then delete the users table (or execute any other injected SQL).

Impact

  • Type: SQL Injection
  • Impact: Data Loss (Drop Table), potentially Data Exfiltration or Modification depending on database permissions.
  • Who is impacted: Appsmith server instances.

References

@subrata71 subrata71 published to appsmithorg/appsmith Apr 22, 2026
Published to the GitHub Advisory Database Apr 29, 2026
Reviewed Apr 29, 2026

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H

EPSS score

Weaknesses

Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')

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. Learn more on MITRE.

CVE ID

No known CVE

GHSA ID

GHSA-h8cj-hpmg-636v

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.