SMS OTP Authenticator Security & Risk Analysis

wordpress.org/plugins/sms-otp-authenticator

Use this plugin to Verify & Authenticate users without any password through OTP on mobile number. Based on Email to SMS service as clicksend.com etc.

0 active installs v1.4 PHP + WP + Updated Jan 30, 2025
one-time-passwordsms-otp-authenticationsms-otp-authenticatorsms-verification
92
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is SMS OTP Authenticator Safe to Use in 2026?

Generally Safe

Score 92/100

SMS OTP Authenticator has no known CVEs and is actively maintained. It's a solid choice for most WordPress installations.

No known CVEs Updated 1yr ago
Risk Assessment

The "sms-otp-authenticator" v1.4 plugin exhibits a generally strong security posture based on the provided static analysis. The absence of dangerous functions, the exclusive use of prepared statements for SQL queries, and proper output escaping are significant strengths. The plugin also appears to have a minimal attack surface with no unprotected entry points identified, and the presence of capability checks suggests some level of access control is implemented. However, the complete lack of nonce checks across all entry points is a notable concern, especially if any of the two capability checks are not sufficiently robust or are bypassed under specific circumstances. The plugin's vulnerability history is entirely clean, with no recorded CVEs, which is a positive indicator of its past security performance. This clean history, combined with the code signals, suggests a developer who is attentive to common security pitfalls, though the missing nonce checks may be an oversight rather than a deliberate design choice. Overall, while the plugin is built on good foundations, the absence of nonce validation represents a potential weakness that could be exploited.

Key Concerns

  • Missing nonce checks on all entry points
Vulnerabilities
None known

SMS OTP Authenticator Security Vulnerabilities

No known vulnerabilities — this is a good sign.
Version History

SMS OTP Authenticator Release Timeline

v1.4Current
Code Analysis
Analyzed Apr 16, 2026

SMS OTP Authenticator Code Analysis

Dangerous Functions
0
Raw SQL Queries
0
0 prepared
Unescaped Output
0
0 escaped
Nonce Checks
0
Capability Checks
2
File Operations
0
External Requests
0
Bundled Libraries
0
Attack Surface

SMS OTP Authenticator Attack Surface

Entry Points0
Unprotected0
WordPress Hooks 4
actionadmin_initsms-otp-authenticator.php:28
actionadmin_menusms-otp-authenticator.php:29
actionadmin_bar_menusms-otp-authenticator.php:30
actionadmin_enqueue_scriptssms-otp-authenticator.php:31
Maintenance & Trust

SMS OTP Authenticator Maintenance & Trust

Maintenance Signals

WordPress version tested6.7.5
Last updatedJan 30, 2025
PHP min version
Downloads396

Community Trust

Rating0/100
Number of ratings0
Active installs0
Developer Profile

SMS OTP Authenticator Developer Profile

cs7.in

2 plugins · 100 total installs

91
trust score
Avg Security Score
96/100
Avg Patch Time
30 days
View full developer profile
Detection Fingerprints

How We Detect SMS OTP Authenticator

Patterns used to identify this plugin on WordPress sites during automated security audits and web crawling.

Asset Fingerprints

Asset Paths
/wp-content/plugins/sms-otp-authenticator/lib/settings.php
Version Parameters
sms-otp-authenticator/style.css?ver=

HTML / DOM Fingerprints

CSS Classes
smsotpauthn-toolbar-pagesmsotpauthn_menu_item_class
Data Attributes
id="smsotpauthn_enable"id="smsotpauthn_authentication"id="smsotpauthn_table"id="authentication_table"
JS Globals
window.onloaddocument.getElementById("smsotpauthn_enable")document.getElementById("smsotpauthn_authentication")
FAQ

Frequently Asked Questions about SMS OTP Authenticator