Vulnerability · Published Mar 20, 2026 · Assigned by GitHub_M

CVE-2026-33143OneUptime: WhatsApp Webhook Missing Signature Verification

High 8.7

In plain English

A high-severity insufficient verification of data authenticity in oneuptime from OneUptime. Proof-of-concept exploit code is public. The chance it is exploited in the next 30 days is estimated at 0.2% (higher than 9% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.

Severity (CVSS 4.0)8.7High

Exploit odds (30 days)0.2%top 91.3% of all CVEs

Exploited in the wildNo reportsCISA SSVC: poc

Attack toolingNoneno public tooling known

Official 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.

Affected packages & fixed versions

Ecosystem	Package	Fixed in	Advisory
npm	oneuptime	10.0.34	GHSA-g5ph-f57v-mwjc

Affected products (as reported)

Vendor	Product	Versions
OneUptime	oneuptime	< 10.0.34

Weakness: CWE-345 · Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N

References

https://github.com/OneUptime/oneuptime/security/advisories/GHSA-g5ph-f57v-mwjc x_refsource_CONFIRM