WP Wrapper Security & Risk Analysis

wordpress.org/plugins/wp-wrapper

Wrapper for WordPress pages using iFrame. Various options in admin panel

700 active installs v1.2.9 PHP + WP 5.0+ Updated Nov 26, 2024
frameiframejoomlapagewrapper
92
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is WP Wrapper Safe to Use in 2026?

Generally Safe

Score 92/100

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

No known CVEs Updated 1yr ago
Risk Assessment

The "wp-wrapper" plugin version 1.2.9 demonstrates a strong security posture based on the provided static analysis. The plugin exhibits a remarkably small attack surface, with no apparent AJAX handlers, REST API routes, shortcodes, or cron events. Crucially, all identified entry points appear to be protected, indicating a commitment to access control. The code also shows good practices regarding SQL queries, exclusively using prepared statements, and a high percentage of properly escaped output.

Despite the generally positive findings, there is one identified flow with an unsanitized path in the taint analysis, which warrants attention. While the severity is not explicitly classified as critical or high, any unsanitized path is a potential risk for directory traversal or other path manipulation vulnerabilities. The plugin's vulnerability history is clean, with no recorded CVEs, which is a significant strength. This suggests a history of secure development and maintenance.

In conclusion, "wp-wrapper" v1.2.9 appears to be a secure plugin with robust development practices. The lack of known vulnerabilities and a well-controlled attack surface are commendable. The single identified unsanitized path is the primary concern and should be investigated and remediated to maintain this strong security record.

Key Concerns

  • Flow with unsanitized path found
  • Output escaping not fully proper (87%)
Vulnerabilities
None known

WP Wrapper Security Vulnerabilities

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

WP Wrapper Code Analysis

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

Output Escaping

87% escaped30 total outputs
Data Flows
1 unsanitized

Data Flow Analysis

3 flows1 with unsanitized paths
nabwrap_description_option_page (wp-wrapper.php:135)
Source (user input) Sink (dangerous op) Sanitizer Transform Unsanitized Sanitized
Attack Surface

WP Wrapper Attack Surface

Entry Points0
Unprotected0
WordPress Hooks 3
actioninitwp-wrapper.php:91
actionadmin_menuwp-wrapper.php:130
filterthe_contentwp-wrapper.php:131
Maintenance & Trust

WP Wrapper Maintenance & Trust

Maintenance Signals

WordPress version tested6.7.5
Last updatedNov 26, 2024
PHP min version
Downloads53K

Community Trust

Rating100/100
Number of ratings4
Active installs700
Developer Profile

WP Wrapper Developer Profile

nabtron

5 plugins · 1K total installs

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

How We Detect WP Wrapper

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

Asset Fingerprints

HTML / DOM Fingerprints

CSS Classes
wp-wrapper-iframe
Data Attributes
id="wp-wrapper-iframe"
Shortcode Output
<iframe class="wp-wrapper-iframe" id="wp-wrapper-iframe" width="
FAQ

Frequently Asked Questions about WP Wrapper