---
id: "CVE-2026-121557"
kind: "vulnerability"
aliases: ["CVE-2026-121557"]
title: "WPPConnect Server: missing auth lets anyone send WhatsApp messages"
severity: "high"
cvss: 8.2
epss: null
exploited: false
status: "open"
category: "ai-tooling"
products: [{"name": "wppconnect-server", "fixed": [], "affected": "<= 2.10.74", "ecosystem": "npm"}]
ecosystems: []
tags: ["ai-tooling", "chatwoot", "self-hosted", "whatsapp", "wppconnect"]
not_affected_if: ["not-internet-reachable", "route-not-exposed"]
published_at: "2026-11-03T16:17:28+00:00"
first_seen_at: "2026-11-03T16:21:44+00:00"
updated_at: "2026-11-03T16:25:38+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-121557", "first_seen_at": "2026-11-03T16:21:44+00:00"}, {"source": "analyst", "url": null, "first_seen_at": "2026-11-03T16:25:38+00:00"}]
---

# WPPConnect Server: missing auth lets anyone send WhatsApp messages

WPPConnect Server through 2.10.74 exposes a Chatwoot webhook route that skips its token check. An unauthenticated attacker who knows or guesses a connected session name can send arbitrary text or files from that WhatsApp account to any number.

_Summary, check and fix written by a model from the sources; labelled as such._

## Affected

- npm:wppconnect-server affected <= 2.10.74 fixed ?

## How to check

- Run your WPPConnect Server version (package.json or the Docker image tag); versions up to and including 2.10.74 are listed as affected.
- In src/routes/index.ts, find the /api/:session/chatwoot route (line ~963 in v2.10.74) and check whether verifyToken is in its middleware chain.
- Test from outside: POST to /api/<session>/chatwoot without an Authorization header. Do this only on your own server. Any response other than 401/403 means the route is open.
- Also check whether the server port (default 21465) is reachable from the internet.

## Timeline

- 2026-11-03T16:21:44+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-121557
- 2026-11-03T16:25:38+00:00 analyst — Read VulnCheck advisory (third-party CNA text only). It lists a fix commit and GitHub issue #2701, but I could not load either, so no fixed version is confirmed. The releases page I could load tops out at v2.10.63, which conflicts with the 2.10.74 affected range. Whether the Chatwoot route is on by default is not stated in the sources. Nothing marked verified.

## Documents

- [advisory] Third-party advisory: www.vulncheck.com https://www.vulncheck.com/advisories/wppconnect-server-through-2.10.74-missing-authentication-via-api-session-chatwoot

## From the sources

WPPConnect Server through 2.10.74 contains a missing authentication vulnerability that allows unauthenticated attackers to send WhatsApp messages by calling the Chatwoot webhook route without verifyToken middleware. Attackers who know or guess a connected session name can POST outgoing message bodies to send arbitrary texts or files from that account to any number.

---

_Free to read at a human pace. An API with keys and an MCP server are in preparation; early access: hello@infrastack.ai_