Transmit SMS Share Security & Risk Analysis

wordpress.org/plugins/transmit-sms-share

Share pages, posts and links via SMS using Transmit SMS API

10 active installs v1.8 PHP + WP 3.3+ Updated Jan 5, 2016
notificationsshare-contentshare-delivery-notificationssmstext-message-notifications
85
A · Safe
CVEs total0
Unpatched0
Last CVENever
Download
Safety Verdict

Is Transmit SMS Share Safe to Use in 2026?

Generally Safe

Score 85/100

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

No known CVEs Updated 10yr ago
Risk Assessment

The transmit-sms-share plugin v1.8 exhibits a mixed security posture. On the positive side, it demonstrates good practices by not having any known CVEs, indicating a generally stable history and responsible maintenance. Furthermore, all SQL queries are properly prepared, and the absence of bundled libraries is also a good sign. However, the static analysis reveals significant concerns. The presence of 8 dangerous functions, specifically 'unserialize', is a major red flag, especially when combined with 3 taint flows with unsanitized paths. This combination strongly suggests a high risk of remote code execution or data manipulation vulnerabilities. The fact that 0% of outputs are properly escaped is also a substantial weakness, opening the door to cross-site scripting (XSS) vulnerabilities. While the attack surface appears small (0 entry points), the underlying code quality issues present a significant risk. The plugin's lack of vulnerability history, while positive, could also be due to a lack of deep security auditing rather than inherent security.

Key Concerns

  • Dangerous functions (unserialize) found
  • Taint flows with unsanitized paths
  • Output escaping is not properly implemented
  • File operations detected
  • External HTTP requests detected
  • No nonce checks implemented
  • Capability checks used minimally
Vulnerabilities
None known

Transmit SMS Share Security Vulnerabilities

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

Transmit SMS Share Code Analysis

Dangerous Functions
8
Raw SQL Queries
0
0 prepared
Unescaped Output
46
0 escaped
Nonce Checks
0
Capability Checks
1
File Operations
1
External Requests
1
Bundled Libraries
0

Dangerous Functions Found

unserialize$TSCOption = unserialize(@get_option(TSCWpOption));admin\admin-controller.php:33
unserialize$TSCOption = unserialize(@get_option(TSCWpOption));admin\admin-controller.php:69
unserialize$TSCOption = unserialize(@get_option(TSCWpOption));admin\admin-controller.php:83
unserialize$TSCOption = unserialize(@get_option(TSCWpOption));admin\admin-controller.php:90
unserialize$TSCSms = unserialize(stripslashes(get_option(TSCWpOptionApi)));admin\admin-functions.php:38
unserialize$TSCOption = unserialize(@get_option(TSCWpOption));admin\admin-functions.php:47
unserialize$this->TSCOption = unserialize($arrOption);classTransmitSareCard.php:12
unserialize$WBSms = unserialize(stripslashes(get_option(TSCWpOptionApi)));classTransmitSareCard.php:66

Output Escaping

0% escaped46 total outputs
Data Flows
3 unsanitized

Data Flow Analysis

4 flows3 with unsanitized paths
TSCSMSC_settingForm (admin\admin-functions.php:35)
Source (user input) Sink (dangerous op) Sanitizer Transform Unsanitized Sanitized
Attack Surface

Transmit SMS Share Attack Surface

Entry Points0
Unprotected0
WordPress Hooks 6
actionadmin_initadmin\admin-functions.php:2
actionwp_enqueue_scriptsadmin\admin-functions.php:23
actionadmin_menuadmin\admin.php:4
filterthe_contentclassTransmitSareCard.php:23
filterwp_headclassTransmitSareCard.php:27
filterwp_footerclassTransmitSareCard.php:115
Maintenance & Trust

Transmit SMS Share Maintenance & Trust

Maintenance Signals

WordPress version tested3.9.40
Last updatedJan 5, 2016
PHP min version
Downloads2K

Community Trust

Rating20/100
Number of ratings1
Active installs10
Developer Profile

Transmit SMS Share Developer Profile

adykidd

1 plugin · 10 total installs

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

How We Detect Transmit SMS Share

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

Asset Fingerprints

Asset Paths
/wp-content/plugins/transmit-sms-share/assets/css/style.css/wp-content/plugins/transmit-sms-share/assets/css/bootstrap.css/wp-content/plugins/transmit-sms-share/assets/font-awesome-4.2.0/css/font-awesome.css/wp-content/plugins/transmit-sms-share/assets/js/bootstrap.js/wp-content/plugins/transmit-sms-share/admin/admin.js
Script Paths
/wp-content/plugins/transmit-sms-share/assets/js/bootstrap.js/wp-content/plugins/transmit-sms-share/admin/admin.js
Version Parameters
transmit-sms-share/assets/css/style.css?ver=transmit-sms-share/assets/css/bootstrap.css?ver=transmit-sms-share/assets/font-awesome-4.2.0/css/font-awesome.css?ver=transmit-sms-share/assets/js/bootstrap.js?ver=transmit-sms-share/admin/admin.js?ver=

HTML / DOM Fingerprints

CSS Classes
TSC_pageafter
Data Attributes
data-toggledata-target
JS Globals
TSCapiConnectTSCrederShortcCodeTSC_successSubmitTSC_failSubmitTSC_phoneFormatWrongTSC_WrongCaptcha+3 more
Shortcode Output
[ARTICLE TITLE][ARTICLE LINK]
FAQ

Frequently Asked Questions about Transmit SMS Share