Skip to content

← Actionable
Medium, CVSS 5.3amended

OneUptime has WhatsApp Resend Verification Authorization Bypass

CVE-2026-30959GHSA-cw6x-mw64-q6pv

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (@oneuptime/common 10.0.21), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Affected packages

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS 4.0
5.3 · 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 · score source
EPSS
  • CVE-2026-30959: 0.39% estimated exploitation activity in the next 30 days; percentile 33.64 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Description 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). Affected Source - Endpoint: UserWhatsAppAPI.ts - Service: UserWhatsAppService.ts - Verify ownership (present in verify endpoint for comparison): UserWhatsAppAPI.ts Full Code Lines (UserWhatsAppAPI.ts) Resend path (authorization gap): Verify path (ownership check present): Prerequisites - Valid attacker account with access to a project - Attacker access token - A victim’s UserWhatsApp itemId belonging to the same project Steps to Reproduce 1. Set your attacker token: 2. Trigger resend for the victim’s item: Expected/Observed Behavior - HTTP 200 with {} body and a new verification code sent to the victim’s phone - No checks confirm that item.userId equals the authenticated user’s ID for the resend path Impact - Spam/DoS against victims’ phone numbers, social engineering pressure,…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 3 · amended ·

    Amended from ghsa record GHSA-cw6x-mw64-q6pv

  2. Revision 2 · amended ·

    Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

  3. Revision 1 · created ·

    Published from osv record GHSA-cw6x-mw64-q6pv

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-30959

Advisory: OneUptime has WhatsApp Resend Verification Authorization Bypass
IDs: CVE-2026-30959, GHSA-cw6x-mw64-q6pv
Record: https://patchnext.com/advisories/cve-2026-30959 (revision 3, source checked 26 Oct 2026, 12:43 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: @oneuptime/common 10.0.21. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm @oneuptime/common: affected < 10.0.21; fixed in 10.0.21

## Suggested inspection (read-only)
- `npm ls @oneuptime/common --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on @oneuptime/common.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-cw6x-mw64-q6pv (OSV record GHSA-cw6x-mw64-q6pv lists affected ranges: npm @oneuptime/common >=0 <10.0.21 (fixed))
- Verified: https://github.com/advisories/GHSA-cw6x-mw64-q6pv (GitHub-reviewed advisory GHSA-cw6x-mw64-q6pv lists affected ranges: npm @oneuptime/common >=0 <10.0.21)

Commands are suggestions: review each one before running it.

Loading voting…