Unauthenticated account takeover via weak OTP verification
Published Jul 22, 2025 · Updated Apr 8, 2026
Authentication bypass in Orion Login with SMS 1.0.5 and earlier allows remote attackers to access any account through weak OTP verification. The olws_handle_verify_phone() function uses an insufficiently strong OTP, exposes the hash used to derive it, and imposes no limit on code attempts. Possession of the target user's phone number is required, and successful exploitation grants that user's access, including Administrator access.
Summary
What happened
Authentication bypass in Orion Login with SMS 1.0.5 and earlier allows remote attackers to access any account through weak OTP verification. The olws_handle_verify_phone() function uses an insufficiently strong OTP, exposes the hash used to derive it, and imposes no limit on code attempts. Possession of the target user's phone number is required, and successful exploitation grants that user's access, including Administrator access.
The record
- CVE
- CVE-2025-7692
- Published
- Jul 22, 2025
- Updated
- Apr 8, 2026
- Vendor
- Imran Sayed
- Product
- Orion Login with SMS
- Classifications
- CWE-288, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 22, 2025CVE publishedPublication date reported by the CVE source.
- Apr 8, 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.
- Affected versionversion=0 <=1.0.5
What conditions does exploitation require?
What is affected?
Published CVSS scores
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.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
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