PT-2026-61653 · Unknown · Whatsapp Mcp Server
CVE-2026-46555
·
Published
2026-07-20
·
Updated
2026-07-20
CVSS v3.1
7.7
High
| Vector | AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N |
Name of the Vulnerable Software and Affected Versions
WhatsApp MCP Server versions prior to 0.2.1
Description
The
whatsapp-bridge HTTP API listens on 127.0.0.1:8080 without authentication or Host header validation. Additionally, the /api/send endpoint accepts an absolute media path parameter without restricting it to a safe directory. These flaws allow a local process running as the same user to send unauthorized WhatsApp messages and read arbitrary files accessible to that user, such as SSH private keys or browser session data, exfiltrating them as document attachments. Furthermore, a remote attacker can trigger these actions via DNS rebinding—a technique that bypasses the Same-Origin Policy to make a browser request to a local IP—if the user visits a malicious webpage.Recommendations
Update to version 0.2.1.
Stop the bridge or block loopback access to port 8080 when not in use.
Avoid running the bridge alongside untrusted MCP servers, browser extensions, or other untrusted local processes.
Avoid browsing untrusted sites while the bridge is running.
Run the bridge under a dedicated user account or in a sandbox/container without access to sensitive files.
Exploit
Fix
Path traversal
Origin Validation Error
Missing Authentication
Found an issue in the description? Have something to add? Feel free to write us 👾
Related Identifiers
Affected Products
Whatsapp Mcp Server