# CVE-2026-30862: Critical Stored XSS & Privilege Escalation in Appsmith

> Stored XSS in Appsmith allows attackers to escalate privileges and take over admin accounts via malicious table widget inputs.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:H`)
- **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:** 9 Mar 2026
- **Updated:** 10 Mar 2026
- **Also known as:** BIT-appsmith-2026-30862, GHSA-5hw4-whxv-6794

## What is CVE-2026-30862?

CVE-2026-30862 is a critical cross-site scripting vulnerability in appsmithorg appsmith, published on 9 Mar 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 is a platform to build admin panels, internal tools, and dashboards. Prior to 1.96, a Critical Stored XSS vulnerability exists in the Table Widget (TableWidgetV2). The root cause is a lack of HTML sanitization in the React component rendering pipeline, allowing malicious attributes to be interpolated into the DOM. By leveraging the "Invite Users" feature, an attacker with a regular user account (user@gmail.com) can force a System Administrator to execute a high-privileged API call (/api/v1/admin/env), resulting in a Full Administrative Account Takeover. This vulnerability is fixed in 1.96.

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

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

1 open source package ship an affected version, including appsmith. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `appsmith` | Bitnami | All versions | 1.96.0 |

Products: Appsmith Appsmith.

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

Upgrade appsmith to 1.96.0 or later.

## Is CVE-2026-30862 being exploited?

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

Public exploit code:

- CVE-2026-30862 | appsmith Privilege Escalation(xss) (github_poc): https://github.com/drkim-dev/CVE-2026-30862

## Other vulnerabilities in appsmithorg 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-50189](https://insights.sbomify.com/CVE-2026-50189/): Appsmith: RCE via Supervisord XML-RPC Admin Interface Exposed via /supervisor Caddy Route (high 8.9)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-30862 is a critical cross-site scripting vulnerability in appsmithorg appsmith, published on 9 Mar 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-30862 exists.

Affected packages and fixed versions:
- appsmith (Bitnami): affected all versions; fixed in 1.96.0

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-30862/ (Markdown: https://insights.sbomify.com/CVE-2026-30862/index.md)
```

## Sources

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

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