WP Front Admin Security & Risk Analysis

wordpress.org/plugins/wp-front-admin

Front-End Admin Panel for Posts, Pages & Custom Post Types Custom Fields

0 active installs v0.3.2 PHP + WP 4.0+ Updated May 18, 2017
adminadministrationfrontfront-endfrontend
85
A · Safe
CVEs total0
Unpatched0
Last CVENever
Download
Safety Verdict

Is WP Front Admin Safe to Use in 2026?

Generally Safe

Score 85/100

WP Front Admin has no known CVEs and is actively maintained. It's a solid choice for most WordPress installations.

No known CVEs Updated 8yr ago
Risk Assessment

The wp-front-admin plugin v0.3.2 exhibits a mixed security posture. On the positive side, there are no known CVEs in its history, and all SQL queries utilize prepared statements, indicating good practices in database interaction. The absence of external HTTP requests and file operations also reduces the attack surface in those areas. However, significant concerns arise from the static analysis. The presence of the `unserialize` function is a critical risk, as it can lead to Remote Code Execution if not handled with extreme caution and proper input validation, especially when dealing with user-supplied data. Furthermore, only 24% of outputs are properly escaped, suggesting a high risk of Cross-Site Scripting (XSS) vulnerabilities. The complete lack of nonce checks on the AJAX handlers is also a major weakness, making them susceptible to Cross-Site Request Forgery (CSRF) attacks. The vulnerability history shows a clean slate, which is a positive indicator, but it does not negate the identified weaknesses in the current version's code.

Key Concerns

  • Dangerous function: unserialize detected
  • Low output escaping coverage (24%)
  • Missing nonce checks on AJAX handlers
Vulnerabilities
None known

WP Front Admin Security Vulnerabilities

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

WP Front Admin Code Analysis

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

Dangerous Functions Found

unserializeecho wpfap_json_indent(json_encode(unserialize(stripslashes(urldecode($data['value'])))));inc\ajax.php:157
unserializeprint_r(unserialize(stripslashes($data['value'])));inc\ajax.php:166
unserialize<pre><?php print_r(unserialize($meta->meta_value)); ?></pre>wp-front-admin.php:198

SQL Query Safety

100% prepared4 total queries

Output Escaping

24% escaped17 total outputs
Data Flows
All sanitized

Data Flow Analysis

3 flows
wpfap_ajax_width (inc\ajax.php:26)
Source (user input) Sink (dangerous op) Sanitizer Transform Unsanitized Sanitized
Attack Surface

WP Front Admin Attack Surface

Entry Points6
Unprotected0

AJAX Handlers 6

authwp_ajax_wpfap_ajax_toggleinc\ajax.php:20
authwp_ajax_wpfap_ajax_widthinc\ajax.php:38
authwp_ajax_wpfap_ajax_cf_updateinc\ajax.php:70
authwp_ajax_wpfap_ajax_cf_addinc\ajax.php:122
authwp_ajax_wpfap_ajax_cf_deleteinc\ajax.php:144
authwp_ajax_wpfap_ajax_edit_serializedinc\ajax.php:172
WordPress Hooks 4
actionadmin_bar_menuinc\hooks.php:3
actionwp_enqueue_scriptswp-front-admin.php:24
actionwp_enqueue_scriptswp-front-admin.php:39
actionwp_footerwp-front-admin.php:47
Maintenance & Trust

WP Front Admin Maintenance & Trust

Maintenance Signals

WordPress version tested4.7.32
Last updatedMay 18, 2017
PHP min version
Downloads1K

Community Trust

Rating100/100
Number of ratings1
Active installs0
Developer Profile

WP Front Admin Developer Profile

Konrad Chmielewski

5 plugins · 130K total installs

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

How We Detect WP Front Admin

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

Asset Fingerprints

Asset Paths
/wp-content/plugins/wp-front-admin/css/bootstrap-wrapper.css/wp-content/plugins/wp-front-admin/css/style.css/wp-content/plugins/wp-front-admin/css/font-awesome.min.css/wp-content/plugins/wp-front-admin/js/script.js
Script Paths
/wp-content/plugins/wp-front-admin/js/script.js
Version Parameters
wp-front-admin/css/bootstrap-wrapper.css?ver=wp-front-admin/css/style.css?ver=wp-front-admin/css/font-awesome.min.css?ver=wp-front-admin/js/script.js?ver=

HTML / DOM Fingerprints

CSS Classes
wpfap_edit_serializedwpfap_edit_serialized_contentwpfap_sidebarwpfap_refreshwpfap_form_cf_addwpfap_form_cf_update
HTML Comments
<!-- <div class="panel-heading"> <div class="pull-right"> <a href="javascript:window.location.reload(true)" class="btn btn-primary btn-xs hide wpfap_refresh" style="margin-top: -5px;"><i class="fa fa-refresh"></i></a> </div> <div class="text-ellipsis" style="max-width:350px;"><strong><?php //echo get_the_title(); ?></strong></div> </div> <div class="panel-footer" style="border-bottom:1px solid #eee;"> <ul class="nav nav-xs nav-pills"> <li role="summary" class="active"><a href="#">Summary</a></li> <li role="cf"><a href="#">Custom Fields</a></li> <li role="comments"><a href="#">Comments</a></li> </ul> </div> -->
Data Attributes
data-widthid="wpfap_edit_serialized"id="wpfap_edit_serialized_content"id="serialized"id="editor_mirror"id="editor"+7 more
JS Globals
wpfap_ajaxwpfap_admin_check_fontawesomewpfap_setupwpfap_setup_add_keyswpfap_empty
FAQ

Frequently Asked Questions about WP Front Admin