Iframe for Gutenberg Security & Risk Analysis

wordpress.org/plugins/dynamic-iframe-for-wp

Easily insert dynamic iframes inside the block editor.

10 active installs v1.1.0 PHP 7.4.0+ WP 5.0.0+ Updated Jun 2, 2024
blockembedexternalgoogle-mapsiframe
92
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is Iframe for Gutenberg Safe to Use in 2026?

Generally Safe

Score 92/100

Iframe for Gutenberg 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 static analysis of the "dynamic-iframe-for-wp" v1.1.0 plugin indicates a strong security posture with no identified vulnerabilities in the analyzed code. The plugin demonstrates excellent adherence to best practices by implementing prepared statements for all SQL queries and ensuring all output is properly escaped. Furthermore, the absence of dangerous functions, file operations, external HTTP requests, and issues in taint analysis suggests a well-hardened codebase. The vulnerability history also shows no recorded CVEs, which is a very positive sign.

While the lack of any detected code signals or taint flows is excellent, it's important to note that the attack surface is reported as zero across all analyzed entry points. This could mean the plugin has no user-facing functionality that would typically create such entry points (like AJAX handlers, REST API routes, or shortcodes), or that these elements are not present in the version analyzed. If the plugin is intended to have interactive features, a zero attack surface might warrant further investigation to ensure all intended functionalities are accounted for in the analysis. However, based on the provided data, the plugin appears to be secure.

Vulnerabilities
None known

Iframe for Gutenberg Security Vulnerabilities

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

Iframe for Gutenberg Code Analysis

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

Iframe for Gutenberg Attack Surface

Entry Points0
Unprotected0
WordPress Hooks 2
actionenqueue_block_assetsdynamic-iframe-for-wp.php:32
actionenqueue_block_editor_assetsdynamic-iframe-for-wp.php:33
Maintenance & Trust

Iframe for Gutenberg Maintenance & Trust

Maintenance Signals

WordPress version tested6.5.8
Last updatedJun 2, 2024
PHP min version7.4.0
Downloads691

Community Trust

Rating0/100
Number of ratings0
Active installs10
Developer Profile

Iframe for Gutenberg Developer Profile

adeleyeayodeji

5 plugins · 1K total installs

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

How We Detect Iframe for Gutenberg

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

Asset Fingerprints

Asset Paths
/wp-content/plugins/dynamic-iframe-for-wp/build/style-index.css/wp-content/plugins/dynamic-iframe-for-wp/build/index.js/wp-content/plugins/dynamic-iframe-for-wp/build/index.css
Script Paths
/wp-content/plugins/dynamic-iframe-for-wp/build/index.js
Version Parameters
dynamic-iframe-for-wp/build/style-index.css?ver=dynamic-iframe-for-wp/build/index.js?ver=dynamic-iframe-for-wp/build/index.css?ver=

HTML / DOM Fingerprints

FAQ

Frequently Asked Questions about Iframe for Gutenberg