WP Subscriber Form Security & Risk Analysis

wordpress.org/plugins/wp-subscriber-form

Adds Feedburner Subscription Form at the end of post content.

10 active installs v1.1 PHP + WP 3.0+ Updated Nov 30, 2012
feedburner-feedback-formfeedburner-formfeedburner-form-at-bottomfeedburner-form-at-the-endsubscriber
85
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is WP Subscriber Form Safe to Use in 2026?

Generally Safe

Score 85/100

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

No known CVEs Updated 13yr ago
Risk Assessment

The wp-subscriber-form plugin v1.1 exhibits a mixed security posture. On the positive side, it demonstrates good practices by having no known CVEs, no unpatched vulnerabilities, and no recorded common vulnerability types. The static analysis also indicates a lack of dangerous functions, file operations, and external HTTP requests. Furthermore, all SQL queries are prepared statements, and a nonce check is present.

However, a significant concern arises from the output escaping. With 100% of outputs unescaped, this presents a clear risk of Cross-Site Scripting (XSS) vulnerabilities. While the taint analysis shows no unsanitized paths, this could be due to the limited scope of analysis or the absence of exploitable flows with the current code. The absence of capability checks on any entry points, though the attack surface is currently reported as zero, could become a problem if new entry points are introduced without proper authorization.

In conclusion, the plugin's lack of historical vulnerabilities and use of prepared statements are strengths. Nevertheless, the pervasive lack of output escaping is a critical weakness that significantly lowers its overall security. This oversight could allow attackers to inject malicious scripts into the WordPress site, potentially leading to session hijacking, defacement, or other harmful actions.

Key Concerns

  • 100% of outputs unescaped
Vulnerabilities
None known

WP Subscriber Form Security Vulnerabilities

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

WP Subscriber Form Code Analysis

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

Output Escaping

0% escaped6 total outputs
Data Flows
All sanitized

Data Flow Analysis

2 flows
handle_options (subscriber-form.php:60)
Source (user input) Sink (dangerous op) Sanitizer Transform Unsanitized Sanitized
Attack Surface

WP Subscriber Form Attack Surface

Entry Points0
Unprotected0
WordPress Hooks 4
filterwp_headsubscriber-form.php:43
filterthe_contentsubscriber-form.php:44
actionadmin_menusubscriber-form.php:45
actionadmin_noticessubscriber-form.php:46
Maintenance & Trust

WP Subscriber Form Maintenance & Trust

Maintenance Signals

WordPress version tested3.4.2
Last updatedNov 30, 2012
PHP min version
Downloads26K

Community Trust

Rating86/100
Number of ratings4
Active installs10
Developer Profile

WP Subscriber Form Developer Profile

Anas Mir

4 plugins · 2K total installs

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

How We Detect WP 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/wp-subscriber-form/subscriber-form.css
Version Parameters
wp-subscriber-form/subscriber-form.css?ver=

HTML / DOM Fingerprints

CSS Classes
headlinearrowtxtsc-subscriber-namesc-subscriber-emailbtn
Data Attributes
id='singlesubscribe'
JS Globals
window.open
Shortcode Output
<div id='singlesubscribe'><span class='headline'><input type='hidden' name='uri' value='<input type='hidden' value='en_US' name='loc'><input type='text' class='txt sc-subscriber-name'
FAQ

Frequently Asked Questions about WP Subscriber Form