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.

Project Subscriptions

No data.

Advisories

No advisories yet.

Fixes

Solution

No solution given by the vendor.


Workaround

No workaround given by the vendor.

History

Tue, 03 Nov 2026 08:45:00 +0000

Type Values Removed Values Added
Weaknesses CWE-200

Tue, 03 Nov 2026 06:15:00 +0000

Type Values Removed Values Added
Description 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.
Title WATI Chat and Notification <= 1.1.8 - Unauthenticated Customer Order PII Disclosure via Leaked API Token
References

Projects

Sign in to view the affected projects.

cve-icon MITRE

Status: PUBLISHED

Assigner: WPScan

Published:

Updated: 2026-11-03T06:00:24.007Z

Reserved: 2026-09-30T13:10:17.510Z

Link: CVE-2026-103379

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2026-11-03T06:17:35.310

Modified: 2026-11-03T06:17:35.310

Link: CVE-2026-103379

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-11-03T08:30:17Z

Weaknesses