CVE-2026-30959

OneUptime has WhatsApp Resend Verification Authorization Bypass

Published Mar 10, 2026 CVSS 4.0 · 5.3 Medium EPSS < 1% KEV · Not listed
Description
OneUptime is a solution for monitoring and managing online services. The resend-verification-code endpoint allows any authenticated user to trigger a verification code resend for any UserWhatsApp record by ID. Ownership is not validated (unlike the verify endpoint). This affects the UserWhatsAppAPI.ts endpoint and the UserWhatsAppService.ts service.

Analysis

AI-generated

Technical impact

The vulnerability lies in the resend-verification-code endpoint of OneUptime’s UserWhatsApp API. Any authenticated user can request a resend of a WhatsApp verification code for any UserWhatsApp record by specifying its ID, while the endpoint does not verify that the requesting user owns the target record. This enables an attacker who has legitimate credentials to obtain a verification code for another user’s WhatsApp account, potentially facilitating account takeover or phishing. The implementation flaw aligns with multiple CWE identifiers, including improper authorization handling.

Affected Systems

Affected systems are deployments of OneUptime’s monitoring solution. The vulnerability applies to versions of the software where the UserWhatsAppAPI.ts and UserWhatsAppService.ts lack ownership checks. Specific version numbers are not listed in the advisory; however, the issue was addressed in the 10.0.21 release noted in the references.

Risk and Exploitability

The CVSS score of 5.3 indicates a medium impact overall, and the EPSS metric reports less than 1% probability of exploitation, suggesting that while the flaw is moderate in severity, it is currently considered unlikely to be actively exploited. Nevertheless, the vulnerability is not listed in the CISA KEV catalog. The attack vector is likely network-based, requiring only an authenticated session; any user with valid credentials could abuse the endpoint. The absence of ownership validation means that nominal security controls are bypassed, giving attackers the same level of access as legitimate users locally.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade to OneUptime 10.0.21 or newer, which removes the ownership validation bug.
  • Restrict the resend-verification-code endpoint to privileged roles only, ensuring only authorized personnel can request resends.
  • Monitor authentication and resend logs for abnormal patterns that may indicate abuse.

Generated by OpenCVE AI on April 16, 2026 at 09:42 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Github GHSA Github GHSA GHSA-cw6x-mw64-q6pv OneUptime has WhatsApp Resend Verification Authorization Bypass
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': 5.0, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:N/A:L'}

Type Values Removed Values Added
First Time appeared Oneuptime
Oneuptime oneuptime
Vendors & Products Oneuptime
Oneuptime oneuptime
Type Values Removed Values Added
Metrics ssvc

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

Type Values Removed Values Added
Description OneUptime is a solution for monitoring and managing online services. The resend-verification-code endpoint allows any authenticated user to trigger a verification code resend for any UserWhatsApp record by ID. Ownership is not validated (unlike the verify endpoint). This affects the UserWhatsAppAPI.ts endpoint and the UserWhatsAppService.ts service.
Title OneUptime has WhatsApp Resend Verification Authorization Bypass
Weaknesses CWE-285
CWE-307
CWE-639
CWE-862
References
Metrics cvssV4_0

{'score': 5.3, 'vector': 'CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:L'}

Weaknesses
  • CWE-285

    Improper Authorization

  • CWE-307

    Improper Restriction of Excessive Authentication Attempts

  • CWE-639

    Authorization Bypass Through User-Controlled Key

  • CWE-862

    Missing Authorization

Sources

Status
PUBLISHED
Assigner
GitHub_M
Published
Updated
Mar 10, 2026, 5:59 PM
Reserved
Mar 7, 2026, 5:34 PM
Status
Analyzed
Published
Mar 10, 2026, 6:18 PM
Modified
Oct 7, 2026, 8:10 AM