CVE-2026-94256: SMS Alert WordPress plugin authentication bypass in OTP login

CVE-2026-94256 · Severity: high · CVSS 8.1 · Published 2026-10-10

The SMS Alert WordPress plugin before version 4.0.1 contains a critical flaw in its one-time password (OTP) login feature that allows attackers to sign in as any user, including administrators, without needing the victim's password. An attacker can complete an OTP code challenge on a phone they control to hijack any account that has a phone number registered, potentially gaining full control of the website.

Quick answers

Is CVE-2026-94256 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-94256 being exploited in the wild.
How severe is CVE-2026-94256?
High severity, with a CVSS score of 8.1, published 10 October 2026.
Which products and versions are affected?
SMS Alert before 4.0.1.
Is there a fix for CVE-2026-94256?
Yes: fixed in 4.0.1. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-94256 attacked?
It is attacked over the network, in a web application.
Am I affected by CVE-2026-94256?
Check whether you run SMS Alert at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • Fixed in: 4.0.1

Technical details

The vulnerability is an authentication bypass (CWE-287) in the OTP login mechanism where the plugin verifies the one-time code validity but fails to confirm that the authenticated account matches the user attempting to log in. An unauthenticated attacker with network access to the login interface can exploit this by providing any target user's phone number, completing the OTP challenge using their own phone, and gaining login access to that user's account. The flaw requires the OTP login feature to be explicitly enabled by the site administrator.

Affected products

  • SMS Alert before 4.0.1

Timeline

  • 2026-10-08: disclosed
  • 2026-10-10: advisory
  • 2026-10-10: patched: Fixed in version 4.0.1

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.