Appsmith SQL editor autocomplete vulnerability (CVE-2026-7299) allows authenticated…
Appsmith SQL editor autocomplete vulnerability (CVE-2026-7299) allows authenticated developers to inject XSS via malicious database object names, enabling session hijacking and privilege escalation.
A stored cross-site scripting vulnerability has been identified in Appsmith's CodeMirror-based SQL query editor autocomplete functionality. The vulnerability stems from inadequate sanitization of database object names before rendering them via innerHTML. An authenticated user with developer-level access to a shared PostgreSQL datasource can create malicious database objects (tables or columns) with names containing JavaScript payloads. When other workspace members trigger SQL autocomplete in the editor, the malicious payload executes in their browser session.
Successful exploitation enables attackers to perform session hijacking, escalate privileges within the Appsmith workspace, or steal credentials from other users. The attack vector requires the attacker to have developer access, which grants permissions to create, edit, and delete applications within assigned workspaces. The vulnerability particularly impacts administrators and other developers who use the SQL editor with shared datasources.
Appsmith version 2.1 addresses this vulnerability. The issue was reported by Stuart Beck and tracked under CVE-2026-7299. Organizations using Appsmith should prioritize updating to version 2.1 or later to remediate this risk.
Mentioned in this report
Detection guidance
Potential Stored XSS Payload in SQL Object Name via Appsmith API Request
Detects HTTP requests to Appsmith datasource/table/column creation endpoints where the submitted object name contains embedded script or event-handler markup, indicating an attempt to stage a stored XSS payload for later execution via the SQL autocomplete renderer. Auto-generated starting point — validate and tune in your environment before deploying. IOC matches can false-positive on shared infrastructure and decay as adversary infrastructure rotates.
title: Potential Stored XSS Payload in SQL Object Name via Appsmith API Request
id: f00fd5c1-a4c4-539f-af14-6ae962d08024
status: experimental
description: 'Detects HTTP POST/PUT requests to Appsmith datasource, table, or column
management endpoints where the request body or query contains HTML/JavaScript injection
markers (e.g. <script, onerror=, javascript:) in a field that would normally hold
a plain database object name. This behaviour matches the attack pattern for CVE-2026-7299,
a stored XSS in the SQL editor autocomplete that renders unsanitized object names
via innerHTML.
'
references:
- CVE-2026-7299
author: Vorant
tags:
- attack.T1059.007
- attack.T1185
- attack.T1078
logsource:
category: webserver
product: appsmith
detection:
selection_endpoint:
cs-method:
- POST
- PUT
cs-uri-stem|contains:
- /api/v1/datasources
- /api/v1/actions
- /api/v1/queries
selection_payload:
cs-uri-query|contains:
- <script
- onerror=
- onload=
- 'javascript:'
- <img
- document.cookie
filter_static_assets:
cs-uri-stem|contains:
- /static/
- /assets/
condition: selection_endpoint and selection_payload and not filter_static_assets
falsepositives:
- Legitimate developers testing SQL query builders with strings that coincidentally
include angle brackets or the word 'script' in column comments
- Automated security scanners intentionally probing the same endpoints with XSS test
strings
level: high
1 more detection artefacts for this report (IOC-atomic rules, Splunk/KQL/Elastic conversions, YARA, Suricata) are available to subscribers.
Behavioural rules are generated from public reporting — validate in your environment before deploying.
Source reporting: https://kb.cert.org/vuls/id/265691
This is the public brief
Subscribers see the full picture: extracted IOCs, ready-to-deploy detections (Sigma, Splunk, KQL, Elastic, YARA, Suricata), the entity graph, TAXII 2.1 feed and real-time alerts matched to your sectors.
Start free