Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Medium, CVSS 4.4amended

Outerbase Studio: Stored XSS in Text Widget Leads to Authentication Token Exposure

CVE-2026-55650GHSA-wwf9-7jrc-rv4q

What to do

Vendor response not established. Follow the primary source's mitigation guidance and check back for a fix.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • npm @outerbase/studio

    Affected
    <= 0.10.2
    Fixed in
    no fixed version recorded

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
4.4 · CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N
EPSS
  • CVE-2026-55650: 0.19% estimated exploitation activity in the next 30 days; percentile 8.79 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Summary A Stored Cross-Site Scripting (XSS) issue previously existed in the Text Widget in Board of Outerbase Studio where unsanitized HTML could be rendered using dangerouslySetInnerHTML Steps to Reproduce 1. Create a new dashboard. 2. Add a Text widget. 3. Insert the following payload: Architectural Context Outerbase Cloud and its backend services were discontinued in 2025. The current version of Outerbase Studio operates purely as a client-side application, with dashboard data stored locally in the browser. Impact In the current architecture, the impact is limited to local self-XSS within a user's browser session. The previously described scenarios involving: - authentication token theft - account takeover - database access are no longer applicable since there are no active backend services or authentication tokens. Remediation The unsafe HTML rendering in the Text Widget has been removed in commit https://github.com/outerbase/studio/commit/b06fb85e5967440278d5a815721b360920566ab9…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 2 · amended ·

    Amended from ghsa record GHSA-wwf9-7jrc-rv4q

  2. Revision 1 · created ·

    Published from osv record GHSA-wwf9-7jrc-rv4q

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-55650

Advisory: Outerbase Studio: Stored XSS in Text Widget Leads to Authentication Token Exposure
IDs: CVE-2026-55650, GHSA-wwf9-7jrc-rv4q
Record: https://patchnext.com/advisories/cve-2026-55650 (revision 2, source checked 26 Oct 2026, 12:56 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 4.4)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm @outerbase/studio: affected <= 0.10.2

## Suggested inspection (read-only)
- `npm ls @outerbase/studio --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on @outerbase/studio.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-wwf9-7jrc-rv4q (OSV record GHSA-wwf9-7jrc-rv4q lists affected ranges: npm @outerbase/studio >=0 <=0.10.2)
- Verified: https://github.com/advisories/GHSA-wwf9-7jrc-rv4q (GitHub-reviewed advisory GHSA-wwf9-7jrc-rv4q lists affected ranges: npm @outerbase/studio >=0 <=0.10.2)

Commands are suggestions: review each one before running it.

Loading voting…