Visual Editor Font Size Security & Risk Analysis

wordpress.org/plugins/visual-editor-font-size

Allows you to change the font size of the visual editor

300 active installs v0.2 PHP + WP 2.8+ Updated Jan 24, 2013
fontfont-sizetinymcevisual-editorwrite-field
85
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is Visual Editor Font Size Safe to Use in 2026?

Generally Safe

Score 85/100

Visual Editor Font Size 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 "visual-editor-font-size" plugin version 0.2 exhibits a mixed security posture. On the positive side, the plugin has a remarkably small attack surface with no registered AJAX handlers, REST API routes, shortcodes, or cron events, and all detected SQL queries are properly prepared. Furthermore, there is no recorded vulnerability history, suggesting a history of stable and secure development.

However, significant concerns arise from the code analysis. The presence of the `create_function` function, a known security risk due to its ability to execute arbitrary PHP code in older PHP versions, is a critical red flag. Additionally, the lack of any output escaping is highly concerning, as it opens the door to Cross-Site Scripting (XSS) vulnerabilities. The absence of nonce checks and capability checks, while not directly exploitable due to the zero attack surface, indicates a lack of robust security practices that could become problematic if the plugin were to evolve and expose new entry points.

In conclusion, while the current limited attack surface and clean vulnerability history are strengths, the identified code signals of `create_function` and unescaped output present immediate and serious risks. The lack of proper security checks for potential future entry points is also a weakness. The plugin should be reviewed and updated to address these critical code issues.

Key Concerns

  • Unescaped output detected
  • Use of dangerous function 'create_function'
  • Missing nonce checks
  • Missing capability checks
Vulnerabilities
None known

Visual Editor Font Size Security Vulnerabilities

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

Visual Editor Font Size Release Timeline

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

Visual Editor Font Size Code Analysis

Dangerous Functions
1
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

Dangerous Functions Found

create_functionadd_filter( 'tiny_mce_before_init', create_function('$a', '$a["setup"] = "visual_editor_font_size_tivisual-editor-font-size.php:18

Output Escaping

0% escaped1 total outputs
Attack Surface

Visual Editor Font Size Attack Surface

Entry Points0
Unprotected0
WordPress Hooks 4
actionadmin_menuvisual-editor-font-size.php:15
filtertiny_mce_before_initvisual-editor-font-size.php:18
actionadmin_print_footer_scriptsvisual-editor-font-size.php:25
actioninitvisual-editor-font-size.php:88
Maintenance & Trust

Visual Editor Font Size Maintenance & Trust

Maintenance Signals

WordPress version tested3.5.2
Last updatedJan 24, 2013
PHP min version
Downloads33K

Community Trust

Rating96/100
Number of ratings8
Active installs300
Developer Profile

Visual Editor Font Size Developer Profile

Nikolay Bachiyski

7 plugins · 1K total installs

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

How We Detect Visual Editor Font Size

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

Asset Fingerprints

HTML / DOM Fingerprints

CSS Classes
visual-editor-font-size-increasevisual-editor-font-size-decreasevisual-editor-font-size-revert
Data Attributes
id="visual-editor-font-size-sample"
JS Globals
visual_editor_font_size_tinymce_setup
FAQ

Frequently Asked Questions about Visual Editor Font Size