# CVE-2026-55650: Outerbase Studio: Stored XSS in Text Widget Leads to Authentication Token Exposure

> Attackers can inject malicious scripts into Text Widgets, leading to self-XSS and potential local token exposure in Outerbase Studio.

- **Severity:** Medium 4.4 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 15 Sep 2026
- **Updated:** 15 Sep 2026
- **Also known as:** GHSA-wwf9-7jrc-rv4q

## What is CVE-2026-55650?

CVE-2026-55650 is a medium-severity cross-site scripting vulnerability in outerbase studio, published on 15 Sep 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

Outerbase Studio is a lightweight browser-based database GUI supporting PostgreSQL, MySQL, and SQLite. In version 0.10.2 and earlier, TextComponent in src/components/chart/index.tsx renders unsanitized Text Widget content through dangerouslySetInnerHTML, allowing injected markup with script-capable event handlers to execute when the widget is displayed. Outerbase Cloud and its backend services were discontinued in 2025, and the current architecture uses local browser dashboard storage, so the impact is limited to local self-XSS. Authentication token theft, account takeover, and backend database access are not applicable to the current architecture. No fixed release is available as of this review.

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

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

2 open source packages ship an affected version, including @outerbase/studio.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `@outerbase/studio` | npm | All versions to 0.10.2 | None |
| `@outerbase/studio` | npm | All versions to 0.10.2 | None |

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

No fix has been published for CVE-2026-55650 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-55650 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-55650 is a medium-severity cross-site scripting vulnerability in outerbase studio, published on 15 Sep 2026. It can only be exploited from the same machine or local 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-55650 exists.

Affected packages and fixed versions:
- @outerbase/studio (npm): affected all versions up to 0.10.2; no fix listed
- @outerbase/studio (npm): affected all versions up to 0.10.2; no fix listed

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

## Sources

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

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