SMSTunnel

By nicunarcisbodea

★ 2.0/5 (1 ratings)0+ active installationsVersion 1.0.19

Send texts from your site through your own Android phone and number: form notifications, sign-in codes, encryption. App on Google Play.

Description

Get the SMSTunnel app on Google Play

SMSTunnel links your WordPress site to your own Android phone. When your site needs to send a text – for example a form or order notification from one of the SMSTunnel add-ons, or a sign-in code – it hands the message to your phone, which sends it from your own number on your own SIM.

You link the site once: open SMSTunnel > Quick Setup, scan the QR code with the SMSTunnel app and approve the connection on your phone. You can remove the connection anytime in the app (Connections); from then on the site can no longer send through your phone. If you connected by signing in or with an API key instead, delete that key anytime in your smstunnel.io dashboard (API Keys).

End-to-end encryption, on every plan. Turn it on in the SMSTunnel settings and your site encrypts its texts for your phone before they leave WordPress, so only your phone can read the words. Sign-in codes (2FA) are the exception: they are not encrypted. We still see the number, your account, your phone and the time. After your phone sends it, a text travels over the mobile network like any other SMS.

With the same account you can also write texts on your computer at smstunnel.io and have your phone send them.

Texts for Fluent Forms and Forminator, built in

If Fluent Forms or Forminator is active on your site, SMSTunnel adds its texts to it. No extra plugin is needed, and both work with the free versions.

  • SMSTunnel SMS – a text to you or your team when someone submits a form. Several numbers allowed; each number gets its own text.
  • SMSTunnel SMS (2) Autoresponder – a confirmation text to the person who filled in the form, at the number they entered.

Messages can include the answers from the form. Numbers must be in international format (+40…); numbers without the country code and premium-rate numbers are skipped.

  • Fluent Forms: open the form, go to Settings & Integrations > Configure Integrations > Add New Integration, and pick SMSTunnel SMS or SMSTunnel SMS (2) Autoresponder. You can switch the integration off in Fluent Forms > Integrations.
  • Forminator: activate SMSTunnel once in Forminator > Integrations. Then open the form, go to its Integrations tab and click + next to SMSTunnel.

SMSTunnel is not affiliated with, endorsed by, or sponsored by WPManageNinja (Fluent Forms) or WPMU DEV / Incsub (Forminator). Fluent Forms and Forminator are trademarks of their owners.

Key Features

  • Your Own Phone and Number – Texts are sent from your SIM, on your mobile plan; recipients see your number and can reply
  • Quick Setup by QR Code – Approve the connection on your phone, remove it anytime from the app
  • Form Notifications – Built-in texts for Fluent Forms and Forminator: to you, and to the person who filled in the form
  • Two-Factor Authentication – Optional SMS codes to secure WordPress logins
  • End-to-End Encryption – Optional; texts of any length, in any alphabet, are encrypted for your phone before they leave your site

Emergency 2FA recovery

When SMS 2FA is required and the “server fallback” option is OFF (the secure default), a total SMS outage would lock every admin out of wp-login – and the fallback option can only be changed while logged in. To recover, edit wp-config.php over FTP/SSH (or use WP-CLI) and add this line above the “That’s all, stop editing” comment:

define('SMSTUNNEL_2FA_EMERGENCY_BYPASS', true);

While this constant is true, admins can log in without entering a 2FA code. Every use is recorded in the PHP error log. Remove the line as soon as SMS delivery is restored. Advanced users can instead hook the ‘smstunnel_2fa_emergency_bypass’ filter and return true.

External Services

This plugin connects to external services to provide certain functionality. Below are the details of each service:

SMSTunnel API

  • Purpose: Core service that enables the plugin to communicate with the SMSTunnel mobile app for sending SMS messages from your phone
  • When data is sent: During Quick Setup (when pairing via QR code), when sending SMS messages (including the texts you set up for Fluent Forms or Forminator forms, each time such a form is submitted), when verifying API connections, and when an administrator opens the Dashboard, the Plugins screen or SMSTunnel > Settings, to check that a phone is linked and online (at most every 10 minutes while no phone is online or the API key is refused, otherwise every 6 hours)
  • Data sent:
    • During setup: Site URL, site token (random identifier), admin email (for account creation)
    • When sending SMS: Phone number, message content (encrypted if E2E is enabled), API key for authentication. For form texts, the message contains the form answers you chose to include
    • When checking your phones: API key only
  • Service provider: SMSTunnel.io (NARBOWEB SRL)
  • Privacy Policy: https://smstunnel.io/privacy
  • Terms of Service: https://smstunnel.io/terms

SMSTunnel Authentication

  • Purpose: Optional sign-in via Google, Facebook, or email to link your SMSTunnel account with WordPress
  • When data is sent: Only when the admin uses the “Connect with Google/Facebook/Email” options on the plugin settings page
  • Data sent:
    • Google/Facebook: Redirects to smstunnel.io/auth/google or smstunnel.io/auth/facebook with a callback URL and CSRF state token
    • Email login: Email and password sent to smstunnel.io/api/v1/auth/login
    • After authentication: Fetches user profile from smstunnel.io/auth/me and creates an API key via smstunnel.io/api/v1/api-keys
  • Service provider: SMSTunnel.io (NARBOWEB SRL)
  • Privacy Policy: https://smstunnel.io/privacy
  • Terms of Service: https://smstunnel.io/terms

Note: QR codes are generated locally using an embedded JavaScript library (qrcode.min.js). No external QR code generation services are used. All SMS messages are sent through your own Android phone – the SMSTunnel server only acts as a relay to connect WordPress with your phone.

Installation

  1. Upload the plugin to /wp-content/plugins/
  2. Activate the plugin
  3. Install the SMSTunnel app on your Android phone from Google Play: https://play.google.com/store/apps/details?id=io.smstunnel.app
  4. Go to SMSTunnel > Quick Setup and scan the QR code with the app
  5. Approve the connection on your phone. To unlink the site later, remove the connection in the app (Connections)
  6. Optional: to get a text when a form is submitted, see “Texts for Fluent Forms and Forminator” in the Description

Screenshots

Changelog

1.0.19

  • Changed: Encrypted texts use the hybrid format (AES-256-GCM with RSA-OAEP) whenever your phone reads it (SMSTunnel app 1.0.8 or newer), so they go out at any length and in any alphabet: Cyrillic, Arabic, Chinese, emoji, letters with diacritics. The “Use hybrid encryption (v2)” setting is gone: it was off unless you turned it on, and without it a text over about 200 Latin letters, or about 35 in other alphabets, could not be encrypted.
  • Improved: For a phone paired with an older app, which reads only RSA, encrypted texts in other alphabets fit two to three times as many letters as before (about 100 Cyrillic or Arabic ones). A text that is still too long gets a clear error: update the app on the phone and pair it again. Settings shows which format your paired phone uses.

1.0.18

  • Fixed: A number written with the trunk prefix in brackets after the country code, such as +49 (0) 170 1234567 or +40 (0)722 123 456, kept the 0 as a digit, so the text went to a wrong number. The (0) is now left out. This also fixes the numbers the SMSTunnel add-ons send to (WooCommerce, Contact Form 7, WPForms, Gravity Forms and the others), because they use this plugin’s check.

1.0.17

  • New: The Dashboard alert also tells you when SMSTunnel can’t connect because the API key was revoked or is invalid, for example after the connection was removed in the app.
  • Improved: SMSTunnel > Settings says whether a phone is linked and online, in the same words as the alert. It no longer waits up to 30 seconds when smstunnel.io doesn’t answer. “Test API Connection” still checks right away and updates the status.
  • Fixed: Disconnect, and “Reset and setup again” in Quick Setup, now forget everything about the account: its phones, the Device ID, the end-to-end encryption pairing and the QR code. If you then connect another account, texts never go to the old phone. Only administrators can disconnect.
  • Fixed: Quick Setup asks smstunnel.io for a QR code only when it shows one, and shows the same code again while it is valid. It used to ask three times on every visit, even after setup.
  • Fixed: “Reset and setup again” in Quick Setup could stop halfway on sites without WooCommerce.
  • Fixed: “Connect with API Key” checks the key only with your SMSTunnel server, the same way “Test API Connection” does.

1.0.16

  • New: An alert on the Dashboard and Plugins screens tells you when your site can’t send texts yet: SMSTunnel isn’t set up, no phone is linked to your account, or your phone hasn’t been online for more than a day. It says what to do next and goes away once that’s done. Administrators can hide it for 7 days; it comes back if the problem is still there.

1.0.15

  • Changed: The links to your SMSTunnel dashboard (your API key, Messages, Register) open the new dashboard at dashboard.smstunnel.io. To let an API key read received texts, open Apps in the dashboard and choose “Allow reading received texts” in the menu of that app.
  • Fixed: The plugin’s home page and the Forminator documentation link went to pages that no longer exist.

1.0.14

  • Fixed: After “Connect with API Key”, Settings now shows the site as connected. The key was saved and texts went out, but the page went back to the connection options.
  • Fixed: The “Send SMS” request of this plugin is now answered by this plugin alone, whatever order plugins load in. It still leaves the order page box of SMSTunnel for WooCommerce 1.0.4 and older to that add-on; from 1.0.5 the add-on has its own request.

1.0.13

  • New: SMS notifications for Fluent Forms and Forminator forms, built in. When one of these plugins is active, you can add “SMSTunnel SMS” (a text to you or your team) and “SMSTunnel SMS (2) Autoresponder” (a confirmation text to the person who filled in the form) to any form. Both work with the free versions.
  • New: Form texts can include the answers from the form, with the form plugin’s own placeholders. “All fields” is sent as one “Label: value” line per answer.
  • Security: Numbers taken from a form must include the country code; premium-rate numbers and short codes are skipped.

1.0.12

  • Changed: Encrypted texts now show who they went to in your SMSTunnel Messages page. The number stays visible to the server; only your phone can read the words.
  • Improved: With hybrid encryption on, texts are padded so their size does not give away how long they are.
  • Changed: The official Google Play badge for the SMSTunnel app now appears in Quick Setup, on the plugin settings page, on the Inbox page of a site that is not linked yet, and in this plugin’s row on the Plugins page.
  • Changed: The plugin description now links to the app on Google Play and explains the optional end-to-end encryption.

1.0.11

  • Fix: The Google Play button in Quick Setup now opens the SMSTunnel app. It used to point to a page that does not exist.
  • Added: A Google Play link next to the QR code option on the plugin settings page.
  • Removed: The App Store button in Quick Setup. SMSTunnel is available for Android only.

1.0.10

  • Changed: For privacy, websites linked to SMSTunnel cannot read the texts your phone receives. The Inbox page now explains this and links to smstunnel.io, where you can read and answer them on your computer. If the site uses a personal API key, the key’s owner can allow it to read received texts in the smstunnel.io dashboard (API Keys).
  • Fix: The Inbox page now shows a clear message instead of a raw error when the site’s API key is invalid or revoked, when smstunnel.io cannot be reached or is temporarily unavailable, and when the rate limit is reached.
  • Fix: Times on the Inbox page are shown in the site’s time zone instead of UTC.
  • Changed: The plugin description now matches the readme.

1.0.9

  • Security: Added an emergency break-glass bypass for 2FA so admins are not permanently locked out of wp-login during a total SMS outage (fail-closed fallback). Enable by adding define(‘SMSTUNNEL_2FA_EMERGENCY_BYPASS’, true); to wp-config.php (see “Emergency 2FA recovery” in Installation), then remove it once access is restored. Every activation is written to the PHP error log.
  • Fix: API validation errors returned by the server as an array (NestJS class-validator) are now flattened to a readable string instead of storing the literal “Array” (PHP 8 “Array to string conversion”).
  • Fix: The read endpoints (connection test, usage, message status, received messages) now handle HTTP 429 rate-limit responses consistently with the send endpoints.
  • Fix: The login 2FA code request is now idempotent – reloading the login page reuses the existing code instead of resending an SMS and burning a rate-limit slot.
  • Fix: Uninstall now also removes the locally generated RSA key pair (smstunnel_public_key, smstunnel_private_key) so no key material is left orphaned.

1.0.8

  • Added: Optional hybrid end-to-end encryption (v2) using AES-256-GCM for the message payload plus RSA-OAEP for the AES key, removing the ~245 byte size limit of legacy RSA encryption for long SMS messages
  • Added: “Use hybrid encryption (v2)” toggle in End-to-End Encryption settings (default OFF; requires an up-to-date SMSTunnel app that advertises v2 support)
  • Added: Pairing now stores the device’s advertised E2E version so the encryptor only uses v2 for capable devices; falls back to v1 otherwise
  • Compatibility: When the hybrid toggle is OFF (default), encryption behaviour is unchanged (RSA PKCS#1 v1.5), so existing paired devices keep working

1.0.7

  • Security: Added rate limiting to public (nopriv) 2FA SMS endpoints to prevent SMS bombing (3 codes / 15 min per IP on login, 60s cooldown + 5/hour on phone-setup verification)
  • Security: Added brute-force lockout on 2FA code verification (max 5 wrong attempts, then the code is invalidated) and switched to constant-time comparison (hash_equals)
  • Security: 2FA server fallback (“login without 2FA when SMS unavailable”) now defaults to OFF to avoid fail-open authentication
  • Security: Client IP detection now relies solely on REMOTE_ADDR (validated) and no longer trusts spoofable proxy headers
  • Security: REST /setup-callback site token now compared in constant time (hash_equals)
  • Security: Hardened admin-settings.js E2E pairing UI to use .text() for dynamic/i18n values (DOM XSS)
  • Security: Added rate-limit (HTTP 429) handling for the SMS API client
  • Security: Strict in_array() comparisons for role checks
  • Fix: Synchronized uninstall cleanup with the option keys actually used by the plugin
  • Added: Shared recipient validation helpers (smstunnel_validate_e164, smstunnel_is_premium_number, smstunnel_sanitize_recipient) for satellite form plugins

1.0.6

  • Security: Added nonce validation (check_ajax_referer) to all nopriv AJAX endpoints including 2FA login and phone setup
  • Security: Fixed DOM XSS in quick-setup.js, social-login.js, and admin-settings.js – all server/URL data now uses .text() instead of .html()
  • Security: Escaped all remaining unescaped outputs in SMS history table
  • Security: API key verification now uses X-API-Key header and configurable server URL (consistent with rest of plugin)
  • Fix: Corrected AJAX action name mismatch for API key verification
  • Documentation: Added SMSTunnel Authentication section to External Services (auth endpoints)

1.0.5

  • Security: Moved all inline JavaScript to external files using wp_enqueue_script and wp_localize_script
  • Security: Added OAuth state parameter validation to prevent CSRF attacks on OAuth callback
  • Security: REST API /setup-callback now validates site_token in permission_callback instead of callback body
  • Security: Removed all wp_add_inline_script calls – all scripts now in external .js files
  • Code: Added $request parameter to all REST API permission_callback methods for PHP 8+ compatibility

1.0.4

  • Documentation: Updated External Services section with complete service documentation

1.0.3

  • Security: Replaced __return_true with documented custom permission_callback methods

1.0.2

  • Security: Replaced inline scripts with wp_add_inline_script for proper enqueueing
  • Security: Fixed XSS vulnerabilities by using textContent instead of innerHTML for server responses
  • Security: Removed external QR code generation services (Google Charts, QR Server API) – all QR codes now generated locally
  • Security: Improved escaping for all JavaScript strings using esc_js()
  • Documentation: Updated External Services section to accurately reflect service usage

1.0.1

  • Security: Added sanitization callbacks for all settings
  • Security: Fixed escape output for translatable strings
  • Security: Database queries now use prepared statements
  • Security: Changed wp_redirect to wp_safe_redirect
  • Security: Changed mt_rand to wp_rand
  • Compatibility: Tested up to WordPress 6.7.1

1.0.0

  • Initial release