WP Themes by Screensize Security & Risk Analysis

wordpress.org/plugins/wp-themes-by-screensize

WP Themes by Screensize will allow you to determine which of two wordpress themes to display to the site visitor depending on their browser width

10 active installs v0.1.1 PHP + WP 3.0.1+ Updated Feb 22, 2012
browserscreensizescreenwidththemeswidth
85
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is WP Themes by Screensize Safe to Use in 2026?

Generally Safe

Score 85/100

WP Themes by Screensize has no known CVEs and is actively maintained. It's a solid choice for most WordPress installations.

No known CVEs Updated 14yr ago
Risk Assessment

The "wp-themes-by-screensize" plugin v0.1.1 exhibits a seemingly strong security posture based on the provided static analysis. There are no identified AJAX handlers, REST API routes, shortcodes, or cron events, resulting in a zero attack surface and no unprotected entry points. The code does not utilize dangerous functions, perform direct file operations, or make external HTTP requests. All SQL queries are handled with prepared statements, which is a positive practice. Taint analysis also reveals no concerning flows. However, a significant concern arises from the output escaping analysis, where 100% of the six identified outputs are not properly escaped. This indicates a high risk of cross-site scripting (XSS) vulnerabilities, as user-supplied data or other dynamic content could be injected into the output without sanitization.

The plugin's vulnerability history is clean, with no recorded CVEs. This, combined with the lack of critical code signals like dangerous functions or raw SQL, initially suggests a low-risk profile. However, the complete absence of output escaping is a critical flaw that overrides the positive indicators. While the plugin appears to have a minimal attack surface and good practices regarding database interaction, the lack of output escaping creates a substantial security hole that malicious actors could exploit. This should be addressed immediately to prevent potential XSS attacks on websites using this plugin.

Key Concerns

  • Outputs not properly escaped
Vulnerabilities
None known

WP Themes by Screensize Security Vulnerabilities

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

WP Themes by Screensize Code Analysis

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

Output Escaping

0% escaped6 total outputs
Attack Surface

WP Themes by Screensize Attack Surface

Entry Points0
Unprotected0
WordPress Hooks 5
actionadmin_menuincludes\admin.php:2
actionadmin_initincludes\admin.php:8
filtertemplateincludes\detectscreensize.php:5
filterstylesheetincludes\detectscreensize.php:6
actioninitincludes\detectscreensize.php:9
Maintenance & Trust

WP Themes by Screensize Maintenance & Trust

Maintenance Signals

WordPress version tested3.2.1
Last updatedFeb 22, 2012
PHP min version
Downloads3K

Community Trust

Rating100/100
Number of ratings2
Active installs10
Developer Profile

WP Themes by Screensize Developer Profile

Adam Sargant

4 plugins · 130 total installs

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

How We Detect WP Themes by Screensize

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

Asset Fingerprints

Asset Paths
/wp-content/plugins/wp-themes-by-screensize/js/aphs_tbs_screensize.js
Script Paths
/wp-content/plugins/wp-themes-by-screensize/js/aphs_tbs_screensize.js

HTML / DOM Fingerprints

JS Globals
aphs_tbs_params
FAQ

Frequently Asked Questions about WP Themes by Screensize