WPPConnect Server through 2.10.74 Missing Authentication via /api/:session/chatwoot
WPPConnect Server through 2.10.74 is affected when a WhatsApp session is connected; the checked facts list no vendor rating and no fixed version.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fix or patch referenced
- Who is exposed
- Default setups
Do first: Check every install: default setups are affected.
- Exploitation?/40Exploitation: unknown (data gap). No CISA SSVC exploitation rating yet
- Exposure22/25Default setups, reachable over the network without a login
- Reach?/20Reach: unknown (data gap). No tracked technology or package matched
- Severity8.2/10CVSS 8.2
- No patch0/5No signal
What would change the score
- Would score about 70 if added to CISA KEV
- Would score about 65 if CISA's SSVC rates exploitation active
CVE-2026-121557 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 8.2 (high) and affects wppconnect-server; a fix or patch is referenced.
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- Published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 30/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Default setups
- Fix
- Fix or patch referenced
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
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.
What to do
Check every install: default setups are affected.
Apply the patch listed under Evidence.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- wppconnect wppconnect-server
through 2.10.74
Evidence 6
- Patch
- Report
- Repository
- Repository
- Repository
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-121557
Is CVE-2026-121557 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
An unauthenticated caller can use the /api/:session/chatwoot endpoint to send arbitrary WhatsApp messages from the victim session's WhatsApp account to arbitrary phone numbers. The report notes this supports impersonation, phishing and spam.Source: github.com
Which versions are affected by CVE-2026-121557?
wppconnect-server: through 2.10.74.Source: cve.now feed data
Am I affected, and how do I check?
The vulnerability is listed as affecting WPPConnect Server through version 2.10.74, the version named in the report. The only runtime condition is that the named WhatsApp session is connected. To check a setup, look up the installed wppconnect-server version and whether the session is connected.Source: github.com
How do I fix CVE-2026-121557?
The checked facts do not name a fixed version, so no specific upgrade target can be given from them. Until a fix is confirmed, check the vendor's release notes for a version later than 2.10.74.Source: github.com