Amplify Security & Risk Analysis

wordpress.org/plugins/amplify

Helping Ecommerce Companies drive more sales and customer happiness.

10 active installs v1.0.1 PHP + WP 3.1+ Updated Nov 19, 2014
customer-servicedesk-jobhelp-deskhelp-desk-softwareservice-management
85
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is Amplify Safe to Use in 2026?

Generally Safe

Score 85/100

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

No known CVEs Updated 11yr ago
Risk Assessment

The 'amplify' plugin version 1.0.1 exhibits a mixed security posture. A significant concern is the presence of an unprotected AJAX handler, representing a direct entry point that lacks authentication. While the plugin shows good practice in its handling of SQL queries, utilizing prepared statements exclusively, this is overshadowed by a concerning 90% of output not being properly escaped. This could lead to cross-site scripting (XSS) vulnerabilities if user-supplied data is directly outputted without sanitization. The taint analysis reveals a high number of flows with unsanitized paths, although none reached critical or high severity, indicating potential for issues if data processing logic is altered or expanded. Encouragingly, the plugin has no recorded vulnerability history, suggesting a generally stable codebase or a lack of targeted discovery. However, the absence of historical vulnerabilities doesn't negate the identified risks, particularly the unprotected AJAX endpoint and the widespread output escaping deficiency, which require immediate attention.

Key Concerns

  • Unprotected AJAX handler
  • High percentage of unescaped output
  • Many unsanitized taint flows
  • No nonce checks on AJAX handlers
Vulnerabilities
None known

Amplify Security Vulnerabilities

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

Amplify Code Analysis

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

SQL Query Safety

100% prepared8 total queries

Output Escaping

10% escaped30 total outputs
Data Flows
7 unsanitized

Data Flow Analysis

8 flows7 with unsanitized paths
connect (includes\amplifylogin.php:88)
Source (user input) Sink (dangerous op) Sanitizer Transform Unsanitized Sanitized
Attack Surface
1 unprotected

Amplify Attack Surface

Entry Points1
Unprotected1

AJAX Handlers 1

authwp_ajax_verify_keyindex.php:61
WordPress Hooks 11
actionwp_enqueue_scriptsincludes\amplifylogin.php:57
actionadmin_menuincludes\amplifylogin.php:61
actionwp_footerincludes\amplifylogin.php:63
actionwp_headincludes\amplifylogin.php:64
actionlogin_enqueue_scriptsincludes\amplifylogin.php:65
filtermce_external_pluginsincludes\amplifylogin.php:425
filtermce_buttonsincludes\amplifylogin.php:426
actionadmin_noticesindex.php:45
actioninitindex.php:53
filterlogin_formindex.php:91
actionregister_formindex.php:92
Maintenance & Trust

Amplify Maintenance & Trust

Maintenance Signals

WordPress version tested3.7.41
Last updatedNov 19, 2014
PHP min version
Downloads4K

Community Trust

Rating100/100
Number of ratings1
Active installs10
Developer Profile

Amplify Developer Profile

Betaout

2 plugins · 20 total installs

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

How We Detect Amplify

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

Asset Fingerprints

Asset Paths
/wp-content/plugins/amplify/css/common.css
Script Paths
/wp-content/plugins/amplify/js/amplify.js
Version Parameters
ver=1.0.1

HTML / DOM Fingerprints

JS Globals
window.amplifyInitAmplify.identifyAPI_KeyProject_Id
FAQ

Frequently Asked Questions about Amplify