Front End PM – WooCommerce Integration Security & Risk Analysis

wordpress.org/plugins/front-end-pm-woocommerce-integration

User can contact seller directly from product page. Option to set so that user can contact seller only after purchase.

10 active installs v1.1 PHP 5.4+ WP 4.4+ Updated May 31, 2019
front-end-pmpmwcwoocommerce
85
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is Front End PM – WooCommerce Integration Safe to Use in 2026?

Generally Safe

Score 85/100

Front End PM – WooCommerce Integration has no known CVEs and is actively maintained. It's a solid choice for most WordPress installations.

No known CVEs Updated 6yr ago
Risk Assessment

The "front-end-pm-woocommerce-integration" plugin v1.1 exhibits a generally positive security posture based on the provided static analysis. Notably, it has a zero attack surface concerning entry points like AJAX handlers, REST API routes, and shortcodes, and no cron events were detected. The absence of dangerous functions, file operations, and external HTTP requests further strengthens its security. However, a significant concern arises from the complete lack of output escaping on all identified output points. This means that any data displayed by the plugin is susceptible to cross-site scripting (XSS) vulnerabilities if that data originates from user input or other untrusted sources. The plugin's vulnerability history is clean, with no known CVEs, which is a strong indicator of good development practices and diligent security patching. While the absence of known vulnerabilities and a small attack surface are strengths, the 0% output escaping is a critical weakness that exposes users to potential XSS attacks, overshadowing the otherwise positive findings.

Key Concerns

  • 0% of outputs properly escaped
  • No nonce checks detected
  • No capability checks detected
Vulnerabilities
None known

Front End PM – WooCommerce Integration Security Vulnerabilities

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

Front End PM – WooCommerce Integration Release Timeline

v1.1Current
Code Analysis
Analyzed Mar 16, 2026

Front End PM – WooCommerce Integration Code Analysis

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

SQL Query Safety

67% prepared3 total queries

Output Escaping

0% escaped5 total outputs
Attack Surface

Front End PM – WooCommerce Integration Attack Surface

Entry Points0
Unprotected0
WordPress Hooks 9
filterfep_admin_settings_tabsadmin\class-fep-wc-admin-settings.php:19
filterfep_settings_fieldsadmin\class-fep-wc-admin-settings.php:20
actionadmin_initadmin\class-fep-wc-admin-settings.php:62
actionadmin_noticesfront-end-pm-woocommerce-integration.php:24
filterfep_current_user_canfront-end-pm-woocommerce-integration.php:52
filterfep_directory_argumentsfront-end-pm-woocommerce-integration.php:53
filterfep_autosuggestion_argumentsfront-end-pm-woocommerce-integration.php:54
filterwoocommerce_product_tabsfront-end-pm-woocommerce-integration.php:57
actioninitfront-end-pm-woocommerce-integration.php:168
Maintenance & Trust

Front End PM – WooCommerce Integration Maintenance & Trust

Maintenance Signals

WordPress version tested5.2.24
Last updatedMay 31, 2019
PHP min version5.4
Downloads2K

Community Trust

Rating100/100
Number of ratings1
Active installs10
Developer Profile

Front End PM – WooCommerce Integration Developer Profile

Shamim Hasan

6 plugins · 5K total installs

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

How We Detect Front End PM – WooCommerce Integration

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

Asset Fingerprints

HTML / DOM Fingerprints

CSS Classes
fep-error
Shortcode Output
[fep_shortcode_new_message_form
FAQ

Frequently Asked Questions about Front End PM – WooCommerce Integration