High severity · published Mar 20, 2026
CVE-2026-33143
OneUptime: WhatsApp Webhook Missing Signature Verification
7.5
CVSS
0.2%
EPSS
No
On KEV
Description
OneUptime is a solution for monitoring and managing online services. Prior to version 10.0.34, the WhatsApp POST webhook handler (/notification/whatsapp/webhook) processes incoming status update events without verifying the Meta/WhatsApp X-Hub-Signature-256 HMAC signature, allowing any unauthenticated attacker to send forged webhook payloads that manipulate notification delivery status records, suppress alerts, and corrupt audit trails. The codebase already implements proper signature verification for Slack webhooks. This issue has been patched in version 10.0.34.
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Confidentiality
None
Integrity
High
Availability
None
Scope
Unchanged
Exploitation
Is it being used?
Exploit prediction (EPSS)0.2% · higher than 8% of CVEs
Exploited in the wildNo evidence yet
CISA KEVNot listed
Ransomware campaign useNot known
Affected products
Which versions
ON
oneuptime · OneUptime
< 10.0.34 · source: vendor, NVD
Affected product
ON
oneuptime
OneUptime
More from oneuptime
9.9
CVE-2026-45102
OneUptime: RCE due to Node.js' vm module escape via error objects and infinite recursion
9.9
CVE-2026-33396
OneUptime has sandbox escape in Synthetic Monitor Playwright runtime allows project members to execute arbitrary commands on Probe
9.9
CVE-2026-32306
OneUptime ClickHouse SQL Injection via Aggregate Query Parameters
9.9
CVE-2026-30957
OneUptime Synthetic Monitor RCE via exposed Playwright browser object
9.9
CVE-2026-30956
OneUptime has authorization bypass via client‑controlled is-multi-tenant-query header