How severe is GHSA-h8cj-hpmg-636v?

GHSA-h8cj-hpmg-636v has a CVSS score of 7.2/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-h8cj-hpmg-636v?

GHSA-h8cj-hpmg-636v affects the following packages: com.appsmith:interfaces (Maven). Ecosystems affected: Maven.

How do I fix GHSA-h8cj-hpmg-636v?

Update com.appsmith:interfaces to 1.99 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-h8cj-hpmg-636v is resolved across your whole dependency graph.

How do I detect GHSA-h8cj-hpmg-636v in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for com.appsmith:interfaces. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-h8cj-hpmg-636v if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-h8cj-hpmg-636v?

O3 pinpoints whether GHSA-h8cj-hpmg-636v is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-h8cj-hpmg-636v actively exploited in the wild?

No public exploit code has been indexed for GHSA-h8cj-hpmg-636v yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-h8cj-hpmg-636v published, and has it been updated?

GHSA-h8cj-hpmg-636v was published on April 29, 2026 and was last updated on May 5, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕ Maven

GHSA-h8cj-hpmg-636v

HIGH

appsmith has SQL Injection in FilterDataService via Unsafe DROP TABLE Execution

Published

Apr 29, 2026

Updated

May 5, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Blast Radius

1 pkg affected

☕com.appsmith:interfaces

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

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.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`com.appsmith:interfaces`	all versions	1.99

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for com.appsmith:interfaces. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update com.appsmith:interfaces to 1.99 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-h8cj-hpmg-636v is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-h8cj-hpmg-636v is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-h8cj-hpmg-636v. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### 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: ```java public void dropTable(String tableName) { String dropTableQuery = "DROP TABLE " + tableName + ";"; executeDb

O3 Security · Impact-Aware SCA

Is GHSA-h8cj-hpmg-636v in your dependencies?

O3 detects GHSA-h8cj-hpmg-636v across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works