---
id: CVE-2026-103379
title: >-
  WATI Chat and Notification <= 1.1.8 - Unauthenticated Customer Order PII
  Disclosure via Leaked API Token
summary: >-
  The WATI Chat and Notification WordPress plugin through 1.1.8 does not require
  a valid, non-empty secret on a public endpoint that returns its stored API
  token, which an unauthenticated attacker can then present to a second public
  endpoi…
severity: medium
cvss: 5.3
cvssVector: 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N'
cvssSource: adp
cwe:
  - CWE-200
product: WATI Chat and Notification
affected:
  - wati_chat_and_notification <= 1.1.8
ssvc:
  exploitation: none
  automatable: 'yes'
  technicalImpact: partial
  timestamp: '2026-11-04T14:08:54.154574Z'
published: '2026-11-03'
updated: '2026-11-04'
sourceUpdated: '2026-11-04T14:18:24.230Z'
source: CVEORG
sourceUrl: 'https://www.cve.org/CVERecord?id=CVE-2026-103379'
references:
  - url: 'https://wpscan.com/vulnerability/0018daf6-9fbe-4b80-8a9e-60950ddaa4fe/'
tags:
  - cve.org
epss: 0.00206
epssPercentile: 0.10723
ingestedAt: '2026-11-05T21:36:00.382Z'
---

## Overview

The WATI Chat and Notification WordPress plugin through 1.1.8 does not require a valid, non-empty secret on a public endpoint that returns its stored API token, which an unauthenticated attacker can then present to a second public endpoint to obtain the order-received URL of any WooCommerce order and read the customer's name, address, phone number and email address. The endpoints are reachable in the WATI Chat and Notification WordPress plugin through 1.1.8's default state and are closed only once a WATI account is connected.

## Affected

- `wati_chat_and_notification <= 1.1.8`

## Remediation

Refer to the linked advisories for vendor-supplied fixes and affected version ranges.
