
WP Edit Security & Risk Analysis
wordpress.org/plugins/wp-editTake complete control over the WordPress content editor.
Is WP Edit Safe to Use in 2026?
Use With Caution
Score 63/100WP Edit has 1 unpatched vulnerability. Evaluate alternatives or apply available mitigations.
The "wp-edit" plugin v4.0.4 presents a mixed security posture. While it demonstrates some good practices with a significant number of nonce and capability checks, and no external HTTP requests or file operations identified in the static analysis, there are notable areas of concern. The presence of the `create_function` dangerous function is a red flag, as it can be a source of vulnerabilities if not handled with extreme care. Furthermore, the taint analysis reveals two flows with unsanitized paths, which, although not flagged as critical or high severity in this instance, indicate potential avenues for malicious input to reach sensitive parts of the application. The SQL query practices are moderately concerning, with 57% of queries not using prepared statements, increasing the risk of SQL injection.
The plugin's vulnerability history is a significant concern. With one known medium-severity CVE that is currently unpatched, and a history of Cross-site Scripting vulnerabilities, this indicates a pattern of introducing or failing to address input sanitization issues. The fact that the last vulnerability was so recent (2025-06-27) and remains unpatched suggests an ongoing security maintenance problem. While the attack surface is currently reported as having no unprotected entry points, the combination of these code-level issues and the unpatched historical vulnerability warrants caution. The low percentage of properly escaped output (11%) is particularly worrying and strongly correlates with the historical XSS vulnerabilities.
In conclusion, while the plugin has some strengths in its structured use of security checks, the identified dangerous function, unsanitized taint flows, high proportion of unescaped output, and critically, the unpatched historical vulnerability, collectively point to a moderate to high risk. The unpatched CVE is a critical indicator of potential exploitation. Recommendations would focus on immediate patching of known vulnerabilities and a thorough review and remediation of output escaping and input sanitization practices.
Key Concerns
- Unpatched CVE (medium severity)
- Flows with unsanitized paths (2)
- Dangerous function detected (create_function)
- SQL queries not using prepared statements (57%)
- Low percentage of properly escaped output (11%)
- History of XSS vulnerabilities
WP Edit Security Vulnerabilities
CVEs by Year
Severity Breakdown
1 total CVE
WP Edit <= 4.0.4 - Authenticated (Administrator+) Stored Cross-Site Scripting
WP Edit Code Analysis
Dangerous Functions Found
Bundled Libraries
SQL Query Safety
Output Escaping
Data Flow Analysis
WP Edit Attack Surface
Shortcodes 24
WordPress Hooks 77
Maintenance & Trust
WP Edit Maintenance & Trust
Maintenance Signals
Community Trust
WP Edit Alternatives
Frontier Buttons
frontier-buttons
Full control of your WP editor toolbars. Adds Table, Search/Replace, Preview & Code sample tinymce plugins. Enable visual editor for comments.
AddQuicktag
addquicktag
This plugin makes it easy to add Quicktags to the html - and visual-editor.
Visual Editor Custom Buttons
visual-editor-custom-buttons
Visual Editor Custom Buttons lets you add custom buttons to the Wordpress Visual Editor.
Post Editor Buttons Fork
post-editor-buttons-fork
This plugin allows you add your own buttons to the post editor's TEXT mode toolbar.
Manage TinyMCE Editor
manage-tinymce-editor
Add buttons to TinyMCE, WordPress' default visual editor.
WP Edit Developer Profile
5 plugins · 41K total installs
How We Detect WP Edit
Patterns used to identify this plugin on WordPress sites during automated security audits and web crawling.
Asset Fingerprints
/wp-content/plugins/wp-edit/admin/assets/css/wp-edit.css/wp-content/plugins/wp-edit/admin/assets/js/wp-edit.jswp-edit/admin/assets/css/wp-edit.css?ver=wp-edit/admin/assets/js/wp-edit.js?ver=HTML / DOM Fingerprints
wp-edit-wrap<!-- Begin WP Edit Plugin --><!-- End WP Edit Plugin -->wp_edit_script_vars