Vulnerability in Chatwoot (CVE-2026-44707)
Summary
Vulnerability in Chatwoot (CVE-2026-44707). Confidential information can be exposed externally. Mitigation: upgrade to 4.13.0 or later.
Original description
The description as published by the source.
Chatwoot is a customer engagement suite. From 2.14.0 to before 4.13.0, a Pre-Account Takeover (Pre-ATO) vulnerability existed in Chatwoot's authentication flow. Because email confirmation was not enforced before an account became usable, an attacker could pre-register an email address they did not own and set a password. If the legitimate owner of that email later signed in to Chatwoot using Google OAuth (or another OmniAuth provider), the OAuth flow silently confirmed the existing account without invalidating the attacker's pre-set credentials. The attacker could then continue to log in with the password they had originally chosen and access any data the victim subsequently entered into the dashboard, including PII, API keys, and other sensitive information. This vulnerability is fixed in 4.13.0.
Source: NIST National Vulnerability Database 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-44707 has been found in Chatwoot.
Confidential information can be exposed externally. CVSS score: 6.8/10.
What to do: upgrade Chatwoot to 4.13.0 or later.
If unsure, ask your IT team or search "Chatwoot CVE-2026-44707" on the vendor's site.
CVE-2026-44707 (Chatwoot) — CWE-283 / CVSS v3 6.8
Attack vector: remote (network-reachable) / unauthenticated
Patched: 4.13.0 — 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.
A vulnerability (CWE-283) exists in Chatwoot.
Check the vendor advisory for the affected versions of Chatwoot.
Severity: Medium (CVSS 6.8/10). Confidential information can be exposed externally.
Update to 4.13.0.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'Chatwoot' . 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
-
1Identify exposure identify
grep -r 'Chatwoot' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
Chatwootを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade Chatwoot to 4.13.0ステージング環境で 4.13.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- advisory github.com
- advisory github.com
- advisory nvd.nist.gov
- patch github.com
- patch github.com