Aweber Subscriber Form Security & Risk Analysis

wordpress.org/plugins/aweber-subscriber-form

This plugin allows you to add a aweber Email Subscription form widget on your sidebars of wordpress websites and blogs.

10 active installs v1.0.0 PHP + WP 3.5.1+ Updated Unknown
apiaweberemailemail-marketingform
100
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is Aweber Subscriber Form Safe to Use in 2026?

Generally Safe

Score 100/100

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

No known CVEs
Risk Assessment

The "aweber-subscriber-form" plugin version 1.0.0 presents a mixed security profile. On the positive side, it demonstrates excellent practices by utilizing prepared statements for all SQL queries and has no recorded vulnerabilities or CVEs, suggesting a history of stability. The plugin also lacks file operations and external HTTP requests, further reducing potential attack vectors. However, the static analysis reveals critical concerns. The presence of the `create_function` dangerous function is a significant security risk, as it can be exploited for code injection. Furthermore, the output escaping is alarmingly low at only 31%, indicating a high probability of cross-site scripting (XSS) vulnerabilities. The complete absence of nonce checks and capability checks across all entry points (which are currently zero, but if added, would be unprotected) also leaves any potential future additions vulnerable to CSRF and privilege escalation attacks.

Key Concerns

  • Use of dangerous function: create_function
  • Low output escaping percentage
  • Missing nonce checks
  • Missing capability checks
Vulnerabilities
None known

Aweber Subscriber Form Security Vulnerabilities

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

Aweber Subscriber Form Code Analysis

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

Dangerous Functions Found

create_functionadd_action('widgets_init', create_function('', 'return register_widget("AweberSubscriberForm");'));index.php:16

Output Escaping

31% escaped13 total outputs
Attack Surface

Aweber Subscriber Form Attack Surface

Entry Points0
Unprotected0
WordPress Hooks 1
actionwidgets_initindex.php:16
Maintenance & Trust

Aweber Subscriber Form Maintenance & Trust

Maintenance Signals

WordPress version tested4.2.39
Last updatedUnknown
PHP min version
Downloads2K

Community Trust

Rating0/100
Number of ratings0
Active installs10
Developer Profile

Aweber Subscriber Form Developer Profile

Prem Tiwari

10 plugins · 12K total installs

74
trust score
Avg Security Score
93/100
Avg Patch Time
238 days
View full developer profile
Detection Fingerprints

How We Detect Aweber Subscriber Form

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

Asset Fingerprints

Asset Paths
/wp-content/plugins/aweber-subscriber-form/awe-style.css
Version Parameters
aweber-subscriber-form/awe-style.css?ver=

HTML / DOM Fingerprints

CSS Classes
aweber-widgetwidget-containerwidgettitlenameemail
Data Attributes
listnamemeta_adtrackingmeta_messagemeta_requiredmeta_forward_vars
Shortcode Output
<form action="http://www.aweber.com/scripts/addlead.pl" method="post">
FAQ

Frequently Asked Questions about Aweber Subscriber Form