WP Viewport Security & Risk Analysis

wordpress.org/plugins/wp-viewport

A debugging tool that adds a small badge in the corner of the site, showing the current viewport width and height for finding media queries breakpoint …

100 active installs v1.0 PHP + WP + Updated Feb 1, 2013
responsiveviewport
85
A · Safe
CVEs total0
Unpatched0
Last CVENever
Download
Safety Verdict

Is WP Viewport Safe to Use in 2026?

Generally Safe

Score 85/100

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

No known CVEs Updated 13yr ago
Risk Assessment

The "wp-viewport" v1.0 plugin exhibits a very strong security posture based on the static analysis results. There are no identified entry points such as AJAX handlers, REST API routes, shortcodes, or cron events, which significantly limits the attack surface. Furthermore, the absence of dangerous functions, file operations, external HTTP requests, and the use of prepared statements for all SQL queries are excellent security practices. The plugin also demonstrates adherence to security by not bundling external libraries. The lack of any recorded vulnerabilities, CVEs, or common vulnerability types in its history further reinforces its secure design and implementation. The primary concern arising from the analysis is the complete absence of output escaping. This means that any data displayed to users could potentially be vulnerable to cross-site scripting (XSS) attacks if that data is not already sanitized or escaped before being passed to the plugin for output. This single oversight, while significant, is mitigated by the severely restricted attack surface. Overall, "wp-viewport" v1.0 appears to be a very securely coded plugin with a robust approach to preventing common web vulnerabilities, with the critical exception of output sanitization.

Key Concerns

  • 100% of outputs are not properly escaped
Vulnerabilities
None known

WP Viewport Security Vulnerabilities

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

WP Viewport Release Timeline

No version history available.
Code Analysis
Analyzed Mar 16, 2026

WP Viewport Code Analysis

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

Output Escaping

0% escaped1 total outputs
Attack Surface

WP Viewport Attack Surface

Entry Points0
Unprotected0
WordPress Hooks 4
actionwp_enqueue_scriptswp-viewport.php:43
actionadmin_initwp-viewport.php:66
actionadmin_menuwp-viewport.php:83
filterplugin_action_linkswp-viewport.php:160
Maintenance & Trust

WP Viewport Maintenance & Trust

Maintenance Signals

WordPress version tested
Last updatedFeb 1, 2013
PHP min version
Downloads3K

Community Trust

Rating0/100
Number of ratings0
Active installs100
Developer Profile

WP Viewport Developer Profile

wgrivera

1 plugin · 100 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 Viewport

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

Asset Fingerprints

Asset Paths
/wp-content/plugins/wp-viewport/css/viewport.css/wp-content/plugins/wp-viewport/js/viewport.js
Script Paths
/wp-content/plugins/wp-viewport/js/viewport.js

HTML / DOM Fingerprints

Data Attributes
name="wpviewport_options[chk_relative_mq]"name="wpviewport_options[base_font_size]"name="wpviewport_options[chk_default_options_db]"
JS Globals
wpviewport_vars
FAQ

Frequently Asked Questions about WP Viewport