BaseCloud

BaseCloud Shield is a lightweight yet powerful security plugin that enforces Two-Factor Authentication (2FA) on your WordPress login page. Unlike other bloat-heavy plugins, BaseCloud Shield focuses on reliability and flexibility in OTP delivery.
Key Features:
<ul>
<li>Plug & Play: Works immediately using standard WordPress email delivery.</li>
<li>Multi-Recipient System: Send OTPs to the logging-in user, a manager email, or selected users.</li>
<li>Multi-Channel Delivery: Choose multiple delivery methods simultaneously (Email, SendGrid, WhatsApp, SMS, Webhook).</li>
<li>WhatsApp Integration: Send OTPs directly via WhatsApp using Twilio API.</li>
<li>SMS Integration: Deliver OTPs via SMS using Twilio API.</li>
<li>SendGrid API V3: Native integration for high-deliverability emails.</li>
<li>Webhook Support: Connect to custom webhooks for advanced automation flows.</li>
<li>Secure OTPs: 6-digit one-time passwords that expire automatically.</li>
<li>Browser Trust: “Remember this device” functionality to reduce friction for authorized users.</li>
<li>Advanced Attack Protection (v1.4.2): Credential stuffing detection, progressive delays, username enumeration protection.</li>
</ul>
<h3>External Services</h3>
This plugin may connect to external third-party services depending on your configuration. Below is a detailed explanation of what services are used, what data is sent, and when:
SendGrid Email API (Optional)
If you select “SendGrid API” as your delivery method in the plugin settings, this plugin will send data to SendGrid’s email service to deliver one-time password (OTP) codes.
<ul>
<li>Service: SendGrid by Twilio</li>
<li>What it’s used for: Sending two-factor authentication codes via email with improved deliverability</li>
<li>When data is sent: Every time a user attempts to log in and 2FA is enabled</li>
<li>Data sent:
<ul>
<li>Recipient email address (user’s email or manager email if configured)</li>
<li>Sender email address (configured in plugin settings)</li>
<li>Site name</li>
<li>Username attempting to log in</li>
<li>6-digit one-time password code</li>
<li>Email subject and HTML body</li>
</ul>
</li>
<li>API Endpoint: https://api.sendgrid.com/v3/mail/send</li>
<li>Terms of Service: https://www.twilio.com/legal/tos</li>
<li>Privacy Policy: https://www.twilio.com/legal/privacy</li>
</ul>
Important: You must have a SendGrid account and API key to use this feature. You are responsible for complying with SendGrid’s terms of service and ensuring proper data handling practices.
Twilio API for WhatsApp & SMS (Optional)
If you select “WhatsApp” or “SMS” as delivery methods, the plugin will send data to Twilio’s API to deliver one-time password codes.
<ul>
<li>Service: Twilio</li>
<li>What it’s used for: Sending two-factor authentication codes via WhatsApp and/or SMS</li>
<li>When data is sent: Every time a user attempts to log in and 2FA is enabled with WhatsApp/SMS selected</li>
<li>Data sent:
<ul>
<li>Recipient phone number (from user meta field ‘billing_phone’)</li>
<li>Sender phone number (WhatsApp number or SMS number configured in settings)</li>
<li>Site name</li>
<li>Username attempting to log in</li>
<li>6-digit one-time password code</li>
<li>Message body</li>
</ul>
</li>
<li>API Endpoint: https://api.twilio.com/2010-04-01/Accounts/{AccountSid}/Messages.json</li>
<li>Terms of Service: https://www.twilio.com/legal/tos</li>
<li>Privacy Policy: https://www.twilio.com/legal/privacy</li>
</ul>
Important: You must have a Twilio account with WhatsApp and/or SMS capabilities enabled. Phone numbers must be stored in user meta (field: ‘billing_phone’). You are responsible for complying with Twilio’s terms of service.
Custom Webhook (Optional)
If you select “Webhook” as a delivery method, the plugin will send login notification data to a webhook URL you configure.
<ul>
<li>Service: Custom webhook endpoint (configured by you)</li>
<li>What it’s used for: Sending login notifications to external systems for custom processing</li>
<li>When data is sent: Every time a user attempts to log in and 2FA is enabled</li>
<li>Data sent:
<ul>
<li>Site name</li>
<li>Username attempting to log in</li>
<li>User email address</li>
<li>6-digit one-time password code</li>
<li>Recipient information array</li>
<li>Timestamp of login attempt</li>
</ul>
</li>
<li>Endpoint: User-configured webhook URL</li>
</ul>
Important: When using the webhook option, you are responsible for the security and privacy compliance of the endpoint you configure. Ensure your webhook endpoint uses HTTPS and follows proper data protection practices.
Standard WordPress Email (Default)
By default, this plugin uses WordPress’s built-in <code>wp_mail()</code> function, which does not involve any external services unless your WordPress installation is configured to use a third-party SMTP service.

BaseCloud Shield

Enterprise-grade Two-Factor Authentication (2FA) with support for Email, SendGrid API, Webhooks, WhatsApp, and SMS delivery.

rishav001

Rishav AuthNova OTP adds a one-time-password verification layer to core WordPress authentication flows.
Features include:
<ul>
<li>Configurable OTP length and charset (numeric or alphanumeric)</li>
<li>OTP expiry and retry limits with temporary lockouts</li>
<li>Login OTP verification step (after password check)</li>
<li>OTP-gated registration flow</li>
<li>OTP-gated password reset flow</li>
<li>Delivery via wp_mail, SendGrid, and Twilio</li>
<li>OTP storage using hashes (never plaintext)</li>
<li>Resend OTP with cooldown and challenge rotation</li>
</ul>
Security highlights:
<ul>
<li>OTP values are hashed before storage and are never saved as plaintext</li>
<li>OTP hashes use keyed HMAC storage and constant-time verification</li>
<li>OTP challenges expire automatically and enforce retry limits per challenge</li>
<li>Request throttling applies cooldown and exponential backoff per IP and identifier</li>
<li>Lockout windows reduce repeated invalid OTP submissions</li>
<li>Nonces are applied on sensitive form submissions</li>
<li>Public auth responses are intentionally generic to reduce account-enumeration leakage</li>
<li>Delivery uses synchronous-first send with bounded async retry fallback and challenge-level delivery status tracking</li>
</ul>
Security limitations:
<ul>
<li>This plugin does not replace passwords, HTTPS, WAF/rate-limiting at the edge, or secure hosting controls</li>
<li>OTP delivery depends on the configured email/SMS provider uptime and deliverability</li>
<li>Administrators should combine this plugin with standard WordPress hardening and monitoring</li>
</ul>
Reliability notes:
<ul>
<li>OTP delivery is attempted synchronously first to reduce silent failures</li>
<li>If synchronous delivery fails and background delivery is healthy, the plugin schedules bounded retries</li>
<li>If background delivery is unhealthy (for example DISABLE_WP_CRON), fallback queueing is skipped and users receive a retry-safe error</li>
<li>Resend cooldown state is server-authoritative and exposed through a status endpoint used by frontend countdown UX</li>
<li>Background queue payload contains only challenge ID (no raw OTP or destination data)</li>
</ul>
<h3>External Services</h3>
This plugin can connect to third-party services to deliver OTP messages. These services are optional and only used if enabled in plugin settings.
<h4>Twilio (SMS Delivery)</h4>
<ul>
<li>Service: Twilio Programmable Messaging API</li>
<li>Purpose: Send OTP codes by SMS</li>
<li>Data sent: destination phone number, sender phone number, OTP message text, account SID for authentication</li>
<li>Credential handling: Twilio credentials are stored in WordPress options and used only when sending OTP messages</li>
<li>When sent: when OTP delivery method includes SMS and an OTP is generated for login, registration, password reset, or resend</li>
<li>Why sent: to deliver time-sensitive OTP codes to the user by SMS</li>
<li>Terms of Service: https://www.twilio.com/legal/tos</li>
<li>Privacy Policy: https://www.twilio.com/en-us/legal/privacy</li>
</ul>
<h4>SendGrid (Email Delivery)</h4>
<ul>
<li>Service: SendGrid Mail Send API</li>
<li>Purpose: Send OTP codes by email</li>
<li>Data sent: recipient email address, sender email/name, message subject, OTP message body, API key for authentication</li>
<li>Credential handling: SendGrid API key is stored in WordPress options and used only when sending OTP messages</li>
<li>When sent: when email provider is set to SendGrid and an OTP is generated for login, registration, password reset, or resend</li>
<li>Why sent: to deliver time-sensitive OTP codes to the user by email</li>
<li>Terms of Service: https://sendgrid.com/policies/terms/</li>
<li>Privacy Policy: https://sendgrid.com/policies/privacy/</li>
</ul>
<h3>Configuration</h3>
<ol>
<li>Set OTP length, type, expiry, retry limit, and lockout duration.</li>
<li>Choose delivery method: Email, SMS, or Both.</li>
<li>Configure provider credentials for SendGrid and/or Twilio if needed.</li>
<li>Enable or disable OTP on login, registration, and password reset flows.</li>
</ol>

Rishav AuthNova OTP

OTP verification for WordPress login, registration, and password reset using email and SMS delivery.

BaseCloud Shield vs Rishav AuthNova OTP