Customized WYSIWYG Editor Page Widths Security & Risk Analysis

wordpress.org/plugins/customized-wysiwyg-editor-page-widths

Enforces a maximum page width per post type in the WYSIWYG Visual editor so content will wrap according to the design of the front end.

50 active installs v1.0 PHP + WP 3.2.1+ Updated Nov 16, 2011
custom-post-typeseditormarginpage-widthwysiwyg
85
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is Customized WYSIWYG Editor Page Widths Safe to Use in 2026?

Generally Safe

Score 85/100

Customized WYSIWYG Editor Page Widths has no known CVEs and is actively maintained. It's a solid choice for most WordPress installations.

No known CVEs Updated 14yr ago
Risk Assessment

The 'customized-wysiwyg-editor-page-widths' plugin v1.0 demonstrates a strong security posture in several key areas based on the static analysis. Notably, it has no identified AJAX handlers, REST API routes, shortcodes, or cron events, resulting in a zero attack surface. The code also avoids dangerous functions, file operations, and external HTTP requests. All SQL queries are properly prepared, and there are no recorded vulnerabilities in its history. However, a significant concern is the 50% rate of unescaped output, indicating that half of the plugin's outputs are not being properly sanitized, which could expose the site to Cross-Site Scripting (XSS) vulnerabilities if user-controlled data is involved in those outputs. Additionally, the complete absence of nonce checks and capability checks across any potential entry points (though none were found in this analysis) is a weakness that could become a critical issue if the plugin were to evolve and introduce new functionalities without proper security measures.

Key Concerns

  • 50% of outputs are not properly escaped
  • No nonce checks implemented
  • No capability checks implemented
Vulnerabilities
None known

Customized WYSIWYG Editor Page Widths Security Vulnerabilities

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

Customized WYSIWYG Editor Page Widths Release Timeline

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

Customized WYSIWYG Editor Page Widths Code Analysis

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

Output Escaping

50% escaped6 total outputs
Attack Surface

Customized WYSIWYG Editor Page Widths Attack Surface

Entry Points0
Unprotected0
WordPress Hooks 3
actionplugins_loadedemc2_customized_wysiwyg_editor_page_widths.php:28
actionadmin_initemc2_customized_wysiwyg_editor_page_widths.php:36
filtermce_cssemc2_customized_wysiwyg_editor_page_widths.php:63
Maintenance & Trust

Customized WYSIWYG Editor Page Widths Maintenance & Trust

Maintenance Signals

WordPress version tested3.2.1
Last updatedNov 16, 2011
PHP min version
Downloads10K

Community Trust

Rating100/100
Number of ratings1
Active installs50
Developer Profile

Customized WYSIWYG Editor Page Widths Developer Profile

MarcusPope

5 plugins · 7K total installs

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

How We Detect Customized WYSIWYG Editor Page Widths

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

Asset Fingerprints

Asset Paths
/wp-content/plugins/customized-wysiwyg-editor-page-widths/editor_styles.php

HTML / DOM Fingerprints

Data Attributes
name="emc2_wysiwyg_page_widths
FAQ

Frequently Asked Questions about Customized WYSIWYG Editor Page Widths