Description
The SMS Alert WordPress plugin before 3.9.8 does not bind its "mobile verified" session flag to the phone number that was actually verified: after an attacker verifies an OTP sent to their own phone, the signup/login handler reads a fresh, attacker-supplied phone number to select the account and logs them in. An unauthenticated attacker can therefore log in as any user, including an administrator, who has a billing phone on file.
Published: 2026-08-02
Score: 7.5 High
EPSS: < 1% Very Low
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

The SMS Alert WordPress plugin fails to tie the "mobile verified" flag to the specific phone number actually verified. As a result, an attacker who successfully verifies the one‑time password (OTP) sent to their own phone can supply any phone number during signup or login. The plugin then looks up the account associated with the supplied number and logs the user in, granting full access to that account, including administrative privileges if a billing phone is registered. This flaw allows an unauthenticated attacker to hijack any user account, achieving a complete breach of confidentiality, integrity, and availability for that account. The weakness maps to authentication bypass through a faulty credential handling process.

Affected Systems

The vulnerability affects the SMS Alert plugin for WordPress versions older than 3.9.8. Any WordPress site that has the plugin installed and permits OTP‑based signup or login is susceptible. The flaw is limited to environments where user accounts have a billing phone stored and the plugin is actively used for account creation or recovery.

Risk and Exploitability

The CVSS score of 7.5 indicates a high severity for unauthenticated account takeover, while the EPSS score of <1% suggests a low overall probability of exploitation. The vulnerability is not listed in the CISA KEV catalog. An attacker can exploit it remotely without prior authentication by sending an OTP to their own number and then providing a target phone number. The absence of binding between the OTP verification flag and the specific phone number makes the exploit trivially simple for anyone who can trigger the OTP workflow.

Generated by OpenCVE AI on August 4, 2026 at 22:07 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Upgrade the SMS Alert plugin to version 3.9.8 or later, which associates the verification flag with the correct phone number.
  • Verify that OTP verification cannot be bypassed by logging in with any arbitrary phone number after a successful OTP delivery.
  • If an upgrade is not immediately possible, consider disabling OTP‑based signup or login until the plugin is fixed, or remove the plugin entirely from the site.

Generated by OpenCVE AI on August 4, 2026 at 22:07 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Mon, 03 Aug 2026 18:30:00 +0000

Type Values Removed Values Added
Metrics cvssV3_1

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

ssvc

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


Mon, 03 Aug 2026 09:45:00 +0000

Type Values Removed Values Added
Weaknesses CWE-287

Sun, 02 Aug 2026 06:15:00 +0000

Type Values Removed Values Added
Description The SMS Alert WordPress plugin before 3.9.8 does not bind its "mobile verified" session flag to the phone number that was actually verified: after an attacker verifies an OTP sent to their own phone, the signup/login handler reads a fresh, attacker-supplied phone number to select the account and logs them in. An unauthenticated attacker can therefore log in as any user, including an administrator, who has a billing phone on file.
Title SMS Alert Order Notifications – WooCommerce < 3.9.8 - Unauthenticated Account Takeover via Unbound OTP Verification in Signup-with-Mobile
References

Subscriptions

No data.

cve-icon MITRE

Status: PUBLISHED

Assigner: WPScan

Published:

Updated: 2026-08-03T17:41:55.569Z

Reserved: 2026-07-09T07:30:39.231Z

Link: CVE-2026-15206

cve-icon Vulnrichment

Updated: 2026-08-03T17:41:51.477Z

cve-icon NVD

Status : Received

Published: 2026-08-02T06:16:36.513

Modified: 2026-08-03T18:16:35.160

Link: CVE-2026-15206

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-08-04T22:15:03Z

Weaknesses