Skip to main content
CVE-2026-103379VulnerabilityPublished

The WATI Chat and Notification WordPress plugin through 1.1.8 does not require a valid, non-empty secret on a public

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-103379· High

Not known to be exploited.

Data as of 3 Nov 2026, 07:30 UTC

Severity
High

Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD

Thin evidence

One scorer or none

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 3 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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

ProductAffectedFixed in
WATI Chat and NotificationAffected
  • <=1.1.8
Fixed in–

AI-suggested

The endpoints are closed only once a WATI account is connected. Users should connect a WATI account to secure these endpoints.

Description

The WATI Chat and Notification WordPress plugin through version 1.1.8 exposes a public endpoint that does not require a valid, non-empty secret to access the stored API token. An unauthenticated attacker can exploit this to retrieve the API token and then use it on a second public endpoint to obtain sensitive WooCommerce order information, including customer names, addresses, phone numbers, and email addresses. These endpoints are accessible by default and only become restricted after connecting a WATI account.

References

Community reviews

Loading reviews…