Orion SMS OTP Verification <= 1.1.7 - Authentication Bypass via Account Takeover
Strategic Overview
- Status
- Patched in 2.0.0
- Affected Plugin
- Orion SMS OTP Verification.
- Affected Version
<= 1.1.7- CVSS
- 9.8Critical
- Weakness type
- CWE-288 · Authentication Bypass Using an Alternate Path or Channel
- CVE
CVE-2025-9967
At a glance
CVE-2025-9967 is a critical-severity Authentication Bypass Using an Alternate Path or Channel vulnerability in the Orion SMS OTP Verification. WordPress plugin, affecting versions <= 1.1.7. It carries a CVSS score of 9.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 2.0.0; sites on affected versions should update now. Disclosed October 2025, reported by Jonas Benjamin Friedli.
Vulnerability Overview
The Orion SMS OTP Verification plugin for WordPress is vulnerable to privilege escalation via account takeover in all versions up to, and including, 1.1.7. This is due to the plugin not properly validating a user's identity prior to updating their password. This makes it possible for unauthenticated attackers to change arbitrary user's password to a one-time password if the attacker knows the user's phone number
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.
CWE-288: Authentication Bypass Using an Alternate Path or Channel
Reaching this weakness in Orion SMS OTP Verification. <= 1.1.7 takes a caller who can reach the endpoint. Authentication bypass through an alternate path means the application has a second route to a protected action that skips the checks the primary route performs.
The protection on the main path becomes irrelevant, because the attacker simply uses the route that never asks. For Orion SMS OTP Verification. the fix is 2.0.0: builds <= 1.1.7 are affected, anything from 2.0.0 onward is not.
Remediation
Update to version 2.0.0, or a newer patched version
How does WordSec protect against this?
Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: Orion SMS OTP Verification. 2.0.0 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C