Analysis and contextual insights are available on OpenCVE Cloud.
No solution or workaround provided in the CVE record.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
No advisories yet.
Wed, 04 Nov 2026 15:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
cvssV3_1
|
Tue, 03 Nov 2026 17:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Wordpress-extensions
Wordpress-extensions wati Chat And Notification |
|
| Vendors & Products |
Wordpress-extensions
Wordpress-extensions wati Chat And Notification |
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 |
|
Status: PUBLISHED
Assigner: WPScan
Published:
Updated: 2026-11-04T14:18:24.230Z
Reserved: 2026-09-30T13:10:17.510Z
Link: CVE-2026-103379
Updated: 2026-11-04T14:05:55.355Z
Status : Deferred
Published: 2026-11-03T06:17:35.310
Modified: 2026-11-04T15:17:23.167
Link: CVE-2026-103379
No data.
OpenCVE Enrichment
Updated: 2026-11-04T17:45:07Z
-
CWE-200
Exposure of Sensitive Information to an Unauthorized Actor