CVE-2026-33143

OneUptime: WhatsApp Webhook Missing Signature Verification

Published Mar 20, 2026 CVSS 4.0 · 8.7 High EPSS < 1% KEV · Not listed
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.

Analysis

AI-generated

Technical impact

The vulnerability resides in the WhatsApp webhook handler of OneUptime. Incoming POST requests to /notification/whatsapp/webhook are processed without verifying the Meta/WhatsApp X-Hub-Signature-256 HMAC signature. An attacker can forge payloads that change notification delivery status records, suppress alerts, and corrupt audit trails, compromising the integrity of the monitoring system.

Affected Systems

All OneUptime installations running versions before 10.0.34 are affected. The product is an open-source platform for monitoring and managing online services. The bug is limited to the WhatsApp webhook endpoint.

Risk and Exploitability

With a CVSS base score of 8.7, the flaw is classified as high severity. EPSS indicates a less than 1 % probability of exploitation, and the issue is not listed in the CISA KEV catalog. Exploitation requires only unauthenticated access to the exposed webhook URL over HTTP or HTTPS; no special credentials are needed. An attacker can modify status fields in the database, potentially erasing evidence of incidents and delaying detection of service problems.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade to OneUptime 10.0.34 or newer, where signature verification is implemented.
  • If an upgrade cannot be performed immediately, restrict the /notification/whatsapp/webhook endpoint to trusted IP ranges or internal networks using firewalls or reverse proxies.
  • After upgrading or restricting the endpoint, confirm that signature verification is active by sending a test webhook with an invalid signature and verifying that the request is rejected.
  • Continuously monitor audit logs for unexpected changes to notification status fields and investigate any anomalies promptly.

Generated by OpenCVE AI on March 24, 2026 at 04:09 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Github GHSA Github GHSA GHSA-g5ph-f57v-mwjc OneUptime WhatsApp Webhook Missing Signature Verification
History
Type Values Removed Values Added
First Time appeared Hackerbay
Hackerbay oneuptime
CPEs cpe:2.3:a:hackerbay:oneuptime:*:*:*:*:*:*:*:*
Vendors & Products Hackerbay
Hackerbay oneuptime
Metrics cvssV3_1

{'score': 7.5, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N'}

ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'poc', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Oneuptime
Oneuptime oneuptime
Vendors & Products Oneuptime
Oneuptime oneuptime
Type Values Removed Values Added
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.
Title OneUptime: WhatsApp Webhook Missing Signature Verification
Weaknesses CWE-345
References
Metrics cvssV4_0

{'score': 8.7, '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'}

Weaknesses
  • CWE-345

    Insufficient Verification of Data Authenticity

Sources

Status
PUBLISHED
Assigner
GitHub_M
Published
Updated
Mar 24, 2026, 2:01 AM
Reserved
Mar 17, 2026, 8:35 PM
Status
Analyzed
Published
Mar 20, 2026, 9:17 PM
Modified
Oct 7, 2026, 8:10 AM