Mobile Device Detect Reloaded Security & Risk Analysis

wordpress.org/plugins/mobile-device-detect-reloaded

This wordpress plugin allows to redirect visitors (desktop, mobile) to a custom target URL, which can be specified in admin.

10 active installs v1.4.1 PHP + WP 2.8+ Updated Sep 8, 2014
deviceipadiphonemobileredirect
85
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is Mobile Device Detect Reloaded Safe to Use in 2026?

Generally Safe

Score 85/100

Mobile Device Detect Reloaded has no known CVEs and is actively maintained. It's a solid choice for most WordPress installations.

No known CVEs Updated 11yr ago
Risk Assessment

The "mobile-device-detect-reloaded" plugin v1.4.1 exhibits a mixed security posture. On the positive side, the plugin demonstrates good practices regarding SQL queries, utilizing prepared statements exclusively, and has no recorded vulnerability history, suggesting a history of secure development. Furthermore, there are no external HTTP requests or file operations, which are common vectors for exploits. However, a significant concern arises from the static code analysis, specifically the "Output escaping" metric. With 10 total outputs and 0% properly escaped, this indicates a high risk of Cross-Site Scripting (XSS) vulnerabilities. Any data processed or displayed by the plugin without proper escaping could be manipulated by attackers to inject malicious scripts. Additionally, the taint analysis shows 2 flows with unsanitized paths, which, while not reaching critical or high severity in this analysis, warrants attention as it suggests potential input validation issues that could be exploited in conjunction with other weaknesses. The absence of capability checks and nonce checks on the identified entry points (though the entry point count is zero) further contributes to the overall risk profile, as they are fundamental security measures.

Key Concerns

  • Unescaped output
  • Taint flows with unsanitized paths
  • No capability checks
  • No nonce checks
Vulnerabilities
None known

Mobile Device Detect Reloaded Security Vulnerabilities

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

Mobile Device Detect Reloaded Code Analysis

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

Output Escaping

0% escaped10 total outputs
Data Flows
2 unsanitized

Data Flow Analysis

2 flows2 with unsanitized paths
pluginoptions_update (loadMobileDeviceDetectReloaded.php:353)
Source (user input) Sink (dangerous op) Sanitizer Transform Unsanitized Sanitized
Attack Surface

Mobile Device Detect Reloaded Attack Surface

Entry Points0
Unprotected0
WordPress Hooks 2
actionwp_loadedloadMobileDeviceDetectReloaded.php:110
actionadmin_menuloadMobileDeviceDetectReloaded.php:117
Maintenance & Trust

Mobile Device Detect Reloaded Maintenance & Trust

Maintenance Signals

WordPress version tested4.0.38
Last updatedSep 8, 2014
PHP min version
Downloads6K

Community Trust

Rating100/100
Number of ratings2
Active installs10
Developer Profile

Mobile Device Detect Reloaded Developer Profile

desimon

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 Mobile Device Detect Reloaded

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

Asset Fingerprints

Asset Paths
/wp-content/plugins/mobile-device-detect-reloaded/css/style.css/wp-content/plugins/mobile-device-detect-reloaded/js/mobile_device_detect.js
Script Paths
/wp-content/plugins/mobile-device-detect-reloaded/js/mobile_device_detect.js
Version Parameters
mobile-device-detect-reloaded/css/style.css?ver=mobile-device-detect-reloaded/js/mobile_device_detect.js?ver=

HTML / DOM Fingerprints

JS Globals
mobile_device_detect
FAQ

Frequently Asked Questions about Mobile Device Detect Reloaded