Mango Contact Form Security & Risk Analysis

wordpress.org/plugins/mango-contact-form

Simple and powerfull contact form plugin, send field to admin email.

0 active installs v1.0.0 PHP 5.0+ WP 4.9.2+ Updated Feb 12, 2018
ajax-contact-formcontact-formcontact-to-admin-email
85
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is Mango Contact Form Safe to Use in 2026?

Generally Safe

Score 85/100

Mango Contact Form 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 mango-contact-form plugin v1.0.0 presents a mixed security posture. On the positive side, the plugin demonstrates good practices by using prepared statements for all SQL queries, avoiding file operations and external HTTP requests, and having no known vulnerabilities in its history. This suggests a developer who is conscious of common security pitfalls. However, significant concerns arise from its attack surface. The plugin exposes two AJAX handlers, and critically, both lack any form of authentication or authorization checks. This creates a direct pathway for unauthenticated users to interact with potentially sensitive plugin functionalities, posing a substantial risk. While taint analysis and code signals like dangerous functions show no immediate threats, the lack of capability checks on the AJAX endpoints means that any user, regardless of their WordPress role, could trigger these actions. The presence of a single nonce check is noted but is insufficient to cover all entry points.

Key Concerns

  • AJAX handlers without auth checks
  • Missing capability checks on entry points
Vulnerabilities
None known

Mango Contact Form Security Vulnerabilities

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

Mango Contact Form Code Analysis

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

Output Escaping

75% escaped4 total outputs
Attack Surface
2 unprotected

Mango Contact Form Attack Surface

Entry Points3
Unprotected2

AJAX Handlers 2

authwp_ajax_mango_contact_form_actionincludes\class-mango-contact-form-plugin.php:182
noprivwp_ajax_mango_contact_form_actionincludes\class-mango-contact-form-plugin.php:183

Shortcodes 1

[contact-form] public\class-mango-contact-form-public.php:154
WordPress Hooks 6
actionplugins_loadedincludes\class-mango-contact-form-plugin.php:151
actionadmin_enqueue_scriptsincludes\class-mango-contact-form-plugin.php:166
actionadmin_enqueue_scriptsincludes\class-mango-contact-form-plugin.php:167
actionwp_enqueue_scriptsincludes\class-mango-contact-form-plugin.php:184
actionwp_enqueue_scriptsincludes\class-mango-contact-form-plugin.php:185
actioninitincludes\class-mango-contact-form-plugin.php:186
Maintenance & Trust

Mango Contact Form Maintenance & Trust

Maintenance Signals

WordPress version tested4.9.29
Last updatedFeb 12, 2018
PHP min version5.0
Downloads1K

Community Trust

Rating0/100
Number of ratings0
Active installs0
Developer Profile

Mango Contact Form Developer Profile

jjvasquez

1 plugin · 0 total installs

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

How We Detect Mango Contact Form

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

Asset Fingerprints

Asset Paths
/wp-content/plugins/mango-contact-form/css/mango-contact-form-admin.css/wp-content/plugins/mango-contact-form/js/mango-contact-form-admin.js
Script Paths
/wp-content/plugins/mango-contact-form/js/mango-contact-form-admin.js
Version Parameters
mango-contact-form-admin.css?ver=mango-contact-form-admin.js?ver=

HTML / DOM Fingerprints

FAQ

Frequently Asked Questions about Mango Contact Form