Seattle WordPress Functionality Security & Risk Analysis

wordpress.org/plugins/wpsea-functionality

A functionality plugin is one that provides a common set of functionality that is

10 active installs v0.8.2 PHP + WP 3.0+ Updated May 17, 2015
analyticsgooglemetashortcodewidget
85
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is Seattle WordPress Functionality Safe to Use in 2026?

Generally Safe

Score 85/100

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

No known CVEs Updated 10yr ago
Risk Assessment

The wpsea-functionality plugin v0.8.2 demonstrates a mixed security posture. On the positive side, it has a very small attack surface with only one entry point (a shortcode) and no AJAX handlers or REST API routes that appear to be unprotected. The absence of known CVEs and a clean vulnerability history is also a strong indicator of good security practices to date. However, significant concerns arise from the static code analysis. The plugin performs SQL queries without using prepared statements, which is a critical security flaw that could lead to SQL injection vulnerabilities. Furthermore, a very low percentage (4%) of output is properly escaped, indicating a high risk of cross-site scripting (XSS) vulnerabilities. The taint analysis, while not reporting critical or high severity issues, does show flows with unsanitized paths, reinforcing the concerns about XSS and other injection attacks due to inadequate sanitization and escaping.

Key Concerns

  • SQL queries not using prepared statements
  • Low percentage of output properly escaped
  • Taint flows with unsanitized paths
  • No nonce checks
  • No capability checks
Vulnerabilities
None known

Seattle WordPress Functionality Security Vulnerabilities

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

Seattle WordPress Functionality Code Analysis

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

SQL Query Safety

0% prepared1 total queries

Output Escaping

4% escaped25 total outputs
Data Flows
3 unsanitized

Data Flow Analysis

3 flows3 with unsanitized paths
wpsea_func_contact_form (wpsea-functionality.php:939)
Source (user input) Sink (dangerous op) Sanitizer Transform Unsanitized Sanitized
Attack Surface

Seattle WordPress Functionality Attack Surface

Entry Points1
Unprotected0

Shortcodes 1

[wpsea_contactform] wpsea-functionality.php:85
WordPress Hooks 8
actionwp_enqueue_scriptswpsea-functionality.php:73
actionadmin_initwpsea-functionality.php:75
actionadmin_initwpsea-functionality.php:76
actionadmin_menuwpsea-functionality.php:77
actionwp_dashboard_setupwpsea-functionality.php:79
actionwp_dashboard_setupwpsea-functionality.php:80
actionwp_footerwpsea-functionality.php:83
actionwidgets_initwpsea-functionality.php:1375
Maintenance & Trust

Seattle WordPress Functionality Maintenance & Trust

Maintenance Signals

WordPress version tested4.1.0
Last updatedMay 17, 2015
PHP min version
Downloads2K

Community Trust

Rating0/100
Number of ratings0
Active installs10
Developer Profile

Seattle WordPress Functionality Developer Profile

Ben Lobaugh (blobaugh)

11 plugins · 11K total installs

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

How We Detect Seattle WordPress Functionality

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

Asset Fingerprints

Asset Paths
/wp-content/plugins/wpsea-functionality/wpsea-functionality.php

HTML / DOM Fingerprints

Shortcode Output
wpsea_func_contact_form
FAQ

Frequently Asked Questions about Seattle WordPress Functionality