Re{code} Front HTML Editor Security & Risk Analysis

wordpress.org/plugins/recode-front-html-editor

Frontend HTML editor for WordPress — edit post_content directly on the page and preview changes instantly without a page reload.

0 active installs v3.6.9 PHP 7.4+ WP 5.9+ Updated Mar 18, 2026
content-editorfrontend-editorhtml-editorinline-editorpost-editor
100
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is Re{code} Front HTML Editor Safe to Use in 2026?

Generally Safe

Score 100/100

Re{code} Front HTML Editor has no known CVEs and is actively maintained. It's a solid choice for most WordPress installations.

No known CVEs Updated 2mo ago
Risk Assessment

The 'recode-front-html-editor' plugin v3.6.9 exhibits a strong security posture based on the provided static analysis. It demonstrates excellent adherence to secure coding practices, with 100% of SQL queries using prepared statements and all output properly escaped. The absence of dangerous functions, file operations, and external HTTP requests further contributes to its safety. Crucially, all identified entry points (2 AJAX handlers) are protected by both nonce and capability checks, indicating a robust defense against common web vulnerabilities. The vulnerability history is also clean, with zero recorded CVEs, which suggests a well-maintained and secure codebase over time. The lack of taint analysis findings further reinforces the confidence in the plugin's security. Overall, this plugin appears to be very secure, with no immediate exploitable risks identified in the provided data.

Vulnerabilities
None known

Re{code} Front HTML Editor Security Vulnerabilities

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

Re{code} Front HTML Editor Release Timeline

v3.6.9Current
Code Analysis
Analyzed Apr 16, 2026

Re{code} Front HTML Editor Code Analysis

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

Output Escaping

100% escaped76 total outputs
Attack Surface

Re{code} Front HTML Editor Attack Surface

Entry Points2
Unprotected0

AJAX Handlers 2

authwp_ajax_rfhe_get_contentrecode-front-html-editor.php:29
authwp_ajax_rfhe_save_postrecode-front-html-editor.php:30
WordPress Hooks 6
actionwp_enqueue_scriptsrecode-front-html-editor.php:27
actionwp_footerrecode-front-html-editor.php:28
actionadmin_menurecode-front-html-editor.php:31
actionadmin_initrecode-front-html-editor.php:32
actionadmin_enqueue_scriptsrecode-front-html-editor.php:33
actionactivated_pluginrecode-front-html-editor.php:34
Maintenance & Trust

Re{code} Front HTML Editor Maintenance & Trust

Maintenance Signals

WordPress version tested6.9.4
Last updatedMar 18, 2026
PHP min version7.4
Downloads183

Community Trust

Rating0/100
Number of ratings0
Active installs0
Developer Profile

Re{code} Front HTML Editor Developer Profile

re{code}commerce

2 plugins · 0 total installs

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

How We Detect Re{code} Front HTML Editor

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

Asset Fingerprints

Asset Paths
/wp-content/plugins/recode-front-html-editor/assets/editor.css/wp-content/plugins/recode-front-html-editor/assets/editor.js
Script Paths
/wp-content/plugins/recode-front-html-editor/assets/editor.js
Version Parameters
/wp-content/plugins/recode-front-html-editor/assets/editor.css?ver=/wp-content/plugins/recode-front-html-editor/assets/editor.js?ver=

HTML / DOM Fingerprints

CSS Classes
rfhe-bar-previewrfhe-theme-darkrfhe-theme-lightrfhe-brandrfhe-edit-btnrfhe-edit-actionsrfhe-statusrfhe-save-btn+3 more
Data Attributes
id="rfhe-bar"id="rfhe-brand"id="rfhe-edit-btn"id="rfhe-edit-actions"id="rfhe-status"id="rfhe-save-btn"+3 more
JS Globals
rfheData
REST Endpoints
/wp-json/recode-front-html-editor/v1/settings
FAQ

Frequently Asked Questions about Re{code} Front HTML Editor