Authyo OTP for Met Form Security & Risk Analysis

wordpress.org/plugins/authyo-otp-for-met-form

Integrates Authyo OTP Verification (Email, SMS, WhatsApp, Voice) into MetForm forms.

0 active installs v1.0.3 PHP 7.2+ WP 5.6+ Updated Unknown
metformmetform-otpsmsvalidationwhatsapp
100
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is Authyo OTP for Met Form Safe to Use in 2026?

Generally Safe

Score 100/100

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

No known CVEs
Risk Assessment

The "authyo-otp-for-met-form" plugin version 1.0.3 exhibits a generally strong security posture based on the provided static analysis. A significant strength is the complete absence of unprotected AJAX handlers and REST API routes, indicating that all entry points have appropriate authentication and permission checks in place. The high percentage of properly escaped output (96%) is also a positive indicator, minimizing the risk of cross-site scripting vulnerabilities.

However, a notable concern is the complete lack of SQL query sanitization. All four SQL queries are executed without prepared statements, which presents a significant risk of SQL injection vulnerabilities. While the taint analysis found no specific unsanitized flows, this is likely due to the limited scope of the analysis (0 flows analyzed) and does not negate the inherent risk of raw SQL queries. The plugin's vulnerability history is clean, which is a positive sign, but it doesn't excuse the identified code-level risks. The plugin demonstrates good practice in access control for its entry points but falls short in data sanitization for database interactions.

In conclusion, the plugin has a solid foundation regarding access control for its interfaces. The primary weakness lies in its database interaction, specifically the use of raw SQL queries without prepared statements. While no specific vulnerabilities are recorded in its history, this code-level flaw creates a substantial risk. Users should be aware of this potential SQL injection vector despite the absence of reported CVEs.

Key Concerns

  • SQL queries not using prepared statements
Vulnerabilities
None known

Authyo OTP for Met Form Security Vulnerabilities

No known vulnerabilities — this is a good sign.
Code Analysis
Analyzed Mar 17, 2026

Authyo OTP for Met Form Code Analysis

Dangerous Functions
0
Raw SQL Queries
4
0 prepared
Unescaped Output
5
125 escaped
Nonce Checks
8
Capability Checks
7
File Operations
7
External Requests
6
Bundled Libraries
0

SQL Query Safety

0% prepared4 total queries

Output Escaping

96% escaped130 total outputs
Attack Surface

Authyo OTP for Met Form Attack Surface

Entry Points7
Unprotected0

AJAX Handlers 3

authwp_ajax_authyo_mf_submit_deactivation_feedbackincludes\class-authyo-deactivation.php:25
authwp_ajax_authyo_mf_submit_email_subscriptionincludes\class-authyo-deactivation.php:38
authwp_ajax_authyo_mf_dismiss_email_subscriptionincludes\class-authyo-deactivation.php:39

REST API Routes 4

POST/wp-json/authyo-mf/v1/deactivation-feedbackincludes\class-authyo-deactivation.php:171
POST/wp-json/authyo-mf/v1/settings-save-trackingincludes\class-authyo-deactivation.php:178
POST/wp-json/authyo-otp-for-met-form/v1/sendincludes\class-authyo-frontend.php:60
POST/wp-json/authyo-otp-for-met-form/v1/verifyincludes\class-authyo-frontend.php:66
WordPress Hooks 15
actionadmin_menuincludes\class-authyo-admin.php:9
actionadmin_initincludes\class-authyo-admin.php:10
actionadmin_enqueue_scriptsincludes\class-authyo-admin.php:12
actionadmin_post_authyo_otp_mf_refresh_countriesincludes\class-authyo-admin.php:13
actionadmin_post_authyo_otp_mf_delete_entryincludes\class-authyo-admin.php:14
actionadmin_enqueue_scriptsincludes\class-authyo-deactivation.php:22
actionrest_api_initincludes\class-authyo-deactivation.php:28
actionupdate_option_authyo_otp_mf_settingsincludes\class-authyo-deactivation.php:32
actionadd_option_authyo_otp_mf_settingsincludes\class-authyo-deactivation.php:34
actionadmin_noticesincludes\class-authyo-deactivation.php:37
actionmetform_after_store_form_dataincludes\class-authyo-entries.php:27
actionwp_enqueue_scriptsincludes\class-authyo-frontend.php:13
actionrest_api_initincludes\class-authyo-frontend.php:14
filtermetform_validation_errorsincludes\class-authyo-frontend.php:15
actionelementor/widgets/registerincludes\class-authyo-widgets.php:9
Maintenance & Trust

Authyo OTP for Met Form Maintenance & Trust

Maintenance Signals

WordPress version tested6.9.4
Last updatedUnknown
PHP min version7.2
Downloads200

Community Trust

Rating0/100
Number of ratings0
Active installs0
Developer Profile

Authyo OTP for Met Form Developer Profile

Konceptwise Digital Media Pvt Ltd

10 plugins · 10 total installs

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

How We Detect Authyo OTP for Met Form

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

Asset Fingerprints

Asset Paths
/wp-content/plugins/authyo-otp-for-met-form/assets/css/admin.css/wp-content/plugins/authyo-otp-for-met-form/assets/js/admin.js
Script Paths
/wp-content/plugins/authyo-otp-for-met-form/assets/js/admin.js
Version Parameters
authyo-otp-for-met-form/assets/css/admin.css?ver=authyo-otp-for-met-form/assets/js/admin.js?ver=

HTML / DOM Fingerprints

FAQ

Frequently Asked Questions about Authyo OTP for Met Form