Description
Appsmith’s SQL query editor’s autocomplete functionality fails to sanitize database object names before rendering them in innerHTML, allowing an authenticated Developer to inject persistent XSS by a malicious table or column names triggering arbitrary code execution in the sessions of other workspace members when they interact with the same datasource.
Affected products
appsmith: appsmith
References7
- github.com/appsmithorg/appsmith/pull/41666 Issue TrackingPatchVendor Advisory
- github.com/appsmithorg/appsmith/security/advisories/GHSA-vvxf-f… Vendor Advisory
- github.com/appsmithorg/appsmith/commit/99d69180919981ed9bc54840… Patch
- www.kb.cert.org/vuls/id/265691 PatchThird Party Advisory
- github.com/Stuub/Appsmith-1.98-Stored-XSS-Exploit ExploitThird Party Advisory
- github.com/Stuub/Appsmith-1.98-Stored-XSS-Exploit ExploitThird Party Advisory
- github.com/appsmithorg/appsmith/releases/tag/v2.1 Release Notes
Metrics
- CVSS 3.1
-
5.4
MEDIUM
Score source: NVD
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N - EPSS — exploit probability
- 0% percentile: 28 · as of 15 November 2026
- CWE
- CWE-79
Could this be exploited in your environment?
A patch closes the known hole. A penetration test shows what an attacker can still reach — with proof.