Categories
CVE-2026-28445 high CVSS 8.7

Cross-Site Scripting (XSS) in @typebot.io/js (CVE-2026-28445)

Summary

Cross-site scripting in @typebot.io/js (CVE-2026-28445). Confidential information can be exposed externally. Exploitable via customIcon.svg. Mitigation: upgrade to 0.10.1 or later.

Original description

The description as published by the source.

Typebot is a chatbot builder tool. In versions 3.15.2 and prior, the RatingButton component in the embed package renders the user-controlled customIcon.svg field directly via Solid's innerHTML directive without any sanitization, even though DOMPurify is already a dependency and is used elsewhere in the codebase (e.g., StreamingBubble.tsx). Because rating blocks are not flagged as isUnsafe by the import sanitizer and the builder preview renders bots inline on the builder's own origin (builder.typebot.io) under a CSP permitting 'unsafe-inline', a malicious imported or collaborator-crafted typebot can execute arbitrary HTML/JS in the builder's authenticated context, bypassing the Web Worker sandbox that protects Script blocks during preview. This allows session hijacking and privilege escalation within the builder application. This issue has been fixed in version 3.16.0.

Source: GitHub Security Advisories (Global) NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-28445 has been found in @typebot.io/js.
Attackers can target a specific entry point like customIcon.svg over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 8.7/10.
What to do: upgrade @typebot.io/js to 0.10.1 or later.
If unsure, ask your IT team or search "@typebot.io/js CVE-2026-28445" on the vendor's site.

CVE-2026-28445 (@typebot.io/js) — CWE-79 / CVSS v3 8.7
Attack vector: remote (network-reachable)
Attack surface: customIcon.svg / innerHTML / isUnsafe / RatingButton
Patched: 0.10.1 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

Cross-site scripting (XSS) (CWE-79) exists in @typebot.io/js. Attackers reach the vulnerable code path via customIcon.svg.

📍 Affected scope

Check the vendor advisory for the affected versions of @typebot.io/js. Attack surface: customIcon.svg / innerHTML / isUnsafe / RatingButton.

🔥 Severity

Severity: High (CVSS 8.7/10). Confidential information can be exposed externally.

🔧 How to fix

Update to 0.10.1.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r '@typebot.io/js' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify
    grep -r '@typebot.io/js' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で @typebot.io/js を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch
    Upgrade @typebot.io/js to 0.10.1

    ステージング環境で 0.10.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

npm @typebot.io/js
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"0.10.1"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details