R3DF Beaver Builder TinyMCE Advanced Icon Fix Security & Risk Analysis

wordpress.org/plugins/r3df-beaver-builder-tinymce-advanced-icon-fix

Fixes font icon's not showing in TinyMCE with TinyMCE Advanced and Beaver Builder.

100 active installs v1.0.1 PHP + WP 4.4+ Updated Jul 18, 2016
beaver-buildertinymce-advanced
85
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is R3DF Beaver Builder TinyMCE Advanced Icon Fix Safe to Use in 2026?

Generally Safe

Score 85/100

R3DF Beaver Builder TinyMCE Advanced Icon Fix has no known CVEs and is actively maintained. It's a solid choice for most WordPress installations.

No known CVEs Updated 9yr ago
Risk Assessment

Based on the provided static analysis and vulnerability history, the "r3df-beaver-builder-tinymce-advanced-icon-fix" v1.0.1 plugin exhibits a strong security posture. The absence of any identified dangerous functions, raw SQL queries, unescaped output, file operations, external HTTP requests, or taint flows indicates diligent coding practices focused on security. The plugin also has a clean vulnerability history with no recorded CVEs, further reinforcing its perceived safety.

While the current analysis presents a positive outlook, it's important to note the complete lack of any detected entry points like AJAX handlers, REST API routes, or shortcodes. This could mean the plugin has a very limited functionality, or it might suggest that the static analysis tools were unable to identify these components, which could be a potential blind spot. The bundled TinyMCE library at version 1.0.1, while not explicitly flagged as a vulnerability in this report, represents a potential area of concern if it contains known, unpatched vulnerabilities in later versions. A comprehensive security assessment would ideally involve a more in-depth review of the bundled library's specific version and its known security advisories.

Overall, the plugin appears to be securely developed, adhering to best practices in SQL querying and output escaping, and has no known vulnerabilities. However, the extremely limited attack surface identified and the presence of an older bundled library warrant cautious optimism. Future monitoring for new vulnerabilities and a potential deeper dive into the bundled TinyMCE version's security status are recommended.

Key Concerns

  • Bundled outdated library: TinyMCE v1.0.1
Vulnerabilities
None known

R3DF Beaver Builder TinyMCE Advanced Icon Fix Security Vulnerabilities

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

R3DF Beaver Builder TinyMCE Advanced Icon Fix 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
1

Bundled Libraries

TinyMCE1.0.1
Attack Surface

R3DF Beaver Builder TinyMCE Advanced Icon Fix Attack Surface

Entry Points0
Unprotected0
WordPress Hooks 1
actionwp_enqueue_scriptsr3df-beaver-builder-tinymce-advanced-icon-fix.php:57
Maintenance & Trust

R3DF Beaver Builder TinyMCE Advanced Icon Fix Maintenance & Trust

Maintenance Signals

WordPress version tested4.7.32
Last updatedJul 18, 2016
PHP min version
Downloads4K

Community Trust

Rating100/100
Number of ratings1
Active installs100
Developer Profile

R3DF Beaver Builder TinyMCE Advanced Icon Fix Developer Profile

Rick Radko

5 plugins · 360 total installs

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

How We Detect R3DF Beaver Builder TinyMCE Advanced Icon Fix

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

Asset Fingerprints

Asset Paths
/wp-content/plugins/r3df-beaver-builder-tinymce-advanced-icon-fix/css/style.css
Version Parameters
r3df-beaver-builder-tinymce-advanced-icon-fix/css/style.css?ver=

HTML / DOM Fingerprints

FAQ

Frequently Asked Questions about R3DF Beaver Builder TinyMCE Advanced Icon Fix