CVE-2026-30959Public exploitNetwork attack vector

Authenticated WhatsApp code flooding via unchecked record ownership

Published Mar 10, 2026 · Updated Mar 10, 2026

Authorization bypass in OneUptime before 10.0.21 allows remote authenticated users to resend WhatsApp verification codes for other users. The resend-verification-code route passes a caller-supplied UserWhatsApp itemId to UserWhatsAppService.resendVerificationCode without checking that the record's userId matches the authenticated user. Exploitation requires a valid project account, an access token, and a victim itemId in that project; repeated requests enable phone spam, social-engineering pressure, and potential lockout flows.

CVSS severity5.3
Medium
EPSS probability0.37%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Authorization bypass in OneUptime before 10.0.21 allows remote authenticated users to resend WhatsApp verification codes for other users. The resend-verification-code route passes a caller-supplied UserWhatsApp itemId to UserWhatsAppService.resendVerificationCode without checking that the record's userId matches the authenticated user. Exploitation requires a valid project account, an access token, and a victim itemId in that project; repeated requests enable phone spam, social-engineering pressure, and potential lockout flows.

The record

CVE
CVE-2026-30959
Published
Mar 10, 2026
Updated
Mar 10, 2026
Vendor
OneUptime
Product
OneUptime
Classifications
CWE-862, CWE-639, CWE-285, CWE-307
Attack vector
network
Privileges
authenticated

Timeline

How it unfolded

  1. Mar 10, 2026CVE publishedPublication date reported by the CVE source.
  2. Mar 10, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=< 10.0.21

What conditions does exploitation require?

Attack vectornetwork
Required privilegesauthenticated

What is affected?

OneUptime · OneUptimeversion=< 10.0.21

Published CVSS scores

5.3GitHub, Inc.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
5.0NIST NVDCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:N/A:L

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesauthenticated
Known exploitationUnconfirmed
Public exploitPublished

Weakness, pattern, technique

CWE-862Missing Authorization
CWE-639Authorization Bypass Through User-Controlled Key
CWE-285Improper Authorization
CWE-307Improper Restriction of Excessive Authentication Attempts

Public exploit references

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo