# CVE-2026-7299: CVE-2026-7299

> Authenticated developers can inject persistent XSS via malicious database object names, leading to arbitrary code execution in other users' sessions.

- **Severity:** Medium 6.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 2 Jun 2026
- **Updated:** 2 Jun 2026
- **Also known as:** GHSA-6j63-xfwq-f8vj

## What is CVE-2026-7299?

CVE-2026-7299 is a medium-severity cross-site scripting vulnerability in Appsmith, published on 2 Jun 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official 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.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

## Which versions are affected by CVE-2026-7299?

It affects 1 product.


Products: Appsmith Appsmith.

## How do I fix CVE-2026-7299?

Apply the vendor's patch.

## Is CVE-2026-7299 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-7299 exists.

Public exploit code:

- Automating the exploitation of CVE-2026-7299 - Stored XSS via Database Table/Column Names in SQL Autocomplete within Appsmith =>1.99. Initial discovery 30/03/26 (github_poc): https://github.com/Stuub/Appsmith-1.98-Stored-XSS-Exploit

## Other vulnerabilities in Appsmith

- [CVE-2026-55454](https://insights.sbomify.com/CVE-2026-55454/): Appsmith: Caddy admin API exposed without authentication (critical 9.9)
- [CVE-2024-55964](https://insights.sbomify.com/CVE-2024-55964/): Code injection in n/a (critical 9.8)
- [CVE-2026-22794](https://insights.sbomify.com/CVE-2026-22794/): Account Takeover Vulnerability in Appsmith (critical 9.7)
- [CVE-2026-24042](https://insights.sbomify.com/CVE-2026-24042/): Appsmith public apps can execute unpublished actions (viewMode confusion) (critical 9.4)
- [CVE-2026-30862](https://insights.sbomify.com/CVE-2026-30862/): Critical Stored XSS & Privilege Escalation in Appsmith (critical 9.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-7299 and fix it if it is affected.

What it is: CVE-2026-7299 is a medium-severity cross-site scripting vulnerability in Appsmith, published on 2 Jun 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-7299 exists.

Affected product: Appsmith. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-7299/ (Markdown: https://insights.sbomify.com/CVE-2026-7299/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-7299
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-7299
- OSV: https://osv.dev/vulnerability/CVE-2026-7299

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-7299/
Summaries are generated and may contain mistakes; the official description above is the record.