CVE-2026-103379: WATI Chat and Notification (WordPress plugin) · Information Exposure
Affects WATI Chat and Notification (WordPress plugin)Source CVE Database V5
Not known to be exploited.
Data as of 3 Nov 2026, 06:28 UTC
Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD
Thin evidence
One scorer or noneExploitation evidence
Disclosed: evidence found.
CVE published 3 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| WATI Chat and Notification | Affected
| Fixed in– |
AI-suggested
Users should connect a WATI account to close the vulnerable endpoints. Monitor vendor advisories for any official fixes or updates.
Description
The WATI Chat and Notification WordPress plugin up to version 1.1.8 has a vulnerability where a public endpoint does not require a valid secret to disclose its stored API token. An unauthenticated attacker can use this token at another public endpoint to retrieve sensitive WooCommerce order details, including customer name, address, phone number, and email. These endpoints are accessible by default and only become restricted after connecting a WATI account.