PHP Mobile Redirect Security & Risk Analysis

wordpress.org/plugins/php-mobile-redirect

Easily detect mobile devices and redirect them to the mobile version of your site.

30 active installs v1.4 PHP + WP 3.2+ Updated Jun 5, 2013
mobile-detectmobile-detectionmobile-redirect
85
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is PHP Mobile Redirect Safe to Use in 2026?

Generally Safe

Score 85/100

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

No known CVEs Updated 12yr ago
Risk Assessment

The "php-mobile-redirect" plugin v1.4 exhibits a strong security posture based on the provided static analysis. The absence of any identified AJAX handlers, REST API routes, shortcodes, or cron events with unprotected entry points suggests a minimal attack surface. Furthermore, the code signals indicate a lack of dangerous functions, secure SQL query practices, and no file operations or external HTTP requests, all of which are positive security indicators. The taint analysis also reveals no critical or high severity unsanitized flows.

However, a significant concern arises from the output escaping. With 3 total outputs and 0% properly escaped, this indicates a potential for Cross-Site Scripting (XSS) vulnerabilities. While the vulnerability history is clean, the lack of robust output escaping is a glaring weakness that could be exploited if any user-provided data is ever incorporated into the plugin's output in the future. The absence of nonce and capability checks, while not directly exploitable given the current attack surface, represents missed opportunities for defensive coding practices that could mitigate future risks if the plugin's functionality were to evolve.

In conclusion, while the plugin's current design minimizes direct exploitable attack vectors and demonstrates good practices in areas like SQL querying, the critical flaw in output escaping presents a notable risk. The clean vulnerability history is reassuring but should not overshadow the immediate need to address the unescaped output.

Key Concerns

  • Outputs are not properly escaped
  • Missing nonce checks
  • Missing capability checks
Vulnerabilities
None known

PHP Mobile Redirect Security Vulnerabilities

No known vulnerabilities — this is a good sign.
Version History

PHP Mobile Redirect Release Timeline

v1.4Current
v1.3
v1.2
v1.1.2
v1.1.1
v1.1
v1.0
Code Analysis
Analyzed Apr 16, 2026

PHP Mobile Redirect Code Analysis

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

Output Escaping

0% escaped3 total outputs
Attack Surface

PHP Mobile Redirect Attack Surface

Entry Points0
Unprotected0
WordPress Hooks 3
actioninitincludes/functions.php:3
actionadmin_menuincludes/pmr_admin_form.php:11
actionadmin_initincludes/pmr_admin_form.php:71
Maintenance & Trust

PHP Mobile Redirect Maintenance & Trust

Maintenance Signals

WordPress version tested3.5.2
Last updatedJun 5, 2013
PHP min version
Downloads11K

Community Trust

Rating76/100
Number of ratings9
Active installs30
Developer Profile

PHP Mobile Redirect Developer Profile

Code96

2 plugins · 2K total installs

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

How We Detect PHP Mobile Redirect

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

Asset Fingerprints

Asset Paths
/wp-content/plugins/php-mobile-redirect/css/pmr_style.css/wp-content/plugins/php-mobile-redirect/js/pmr_script.js
Script Paths
/wp-content/plugins/php-mobile-redirect/js/pmr_script.js
Version Parameters
php-mobile-redirect/css/pmr_style.css?ver=php-mobile-redirect/js/pmr_script.js?ver=

HTML / DOM Fingerprints

FAQ

Frequently Asked Questions about PHP Mobile Redirect