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.
Published: 2026-11-03
Score: n/a
EPSS: n/a
KEV: No
Impact: Unauthorized PII Disclosure
Action: Patch Now
AI Analysis

Impact

The plugin fails to enforce a non‑empty secret on a public endpoint that returns the stored API token. An unauthenticated attacker can retrieve this token and then call a second public endpoint that reveals the order‑received URL for any WooCommerce order, exposing the customer’s name, address, phone number and email address. The vulnerability allows full disclosure of personally identifiable information for every order processed through the affected plugin.

Affected Systems

WATI Chat and Notification WordPress plugin, versions 1.1.8 or earlier.

Risk and Exploitability

The exposed endpoints are reachable on any site that has installed the plugin in its default state and are closed only after a WATI account is connected. Because authentication is not required, the attack can be performed remotely from any IP address. The vulnerability is not currently listed in CISA’s KEV catalog and no EPSS score is available, but the information disclosure is severe, potentially impacting customer trust and regulatory compliance. A successful exploitation could lead to extensive personal data exposure and fraud risk for customers.

Generated by OpenCVE AI on November 3, 2026 at 08:21 UTC.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade the WATI Chat and Notification plugin to the latest available version, which removes the publicly accessible token and order‑information endpoints, or uninstall the plugin entirely if an upgrade is not feasible.
  • If an immediate update is not possible, restrict access to the token endpoint by adding authentication requirements or firewall rules that limit calls to trusted IP addresses or only allow authenticated users.
  • Consider disabling the plugin or terminating the WATI integration after ensuring the data is secured and any existing tokens are revoked.

Generated by OpenCVE AI on November 3, 2026 at 08:21 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

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

Subscriptions

No data.

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
  • CWE-200

    Exposure of Sensitive Information to an Unauthorized Actor