i4a Single Sign-On Security & Risk Analysis

wordpress.org/plugins/internet4associations-single-sign-on

Allows a bidirectional single sign-on between a WordPress website and an i4a-hosted website for current members who can sign in to either the WordPres …

10 active installs v3.0 PHP 5.6+ WP 3.0.1+ Updated Feb 2, 2026
amsassociation-managementmembershipsingle-sign-onsso
100
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is i4a Single Sign-On Safe to Use in 2026?

Generally Safe

Score 100/100

i4a Single Sign-On has no known CVEs and is actively maintained. It's a solid choice for most WordPress installations.

No known CVEs Updated 6mo ago
Risk Assessment

The security posture of the internet4associations-single-sign-on plugin v3.0 appears to be generally strong based on the provided static analysis and vulnerability history. The plugin demonstrates good security practices by utilizing prepared statements for all SQL queries, performing nonce checks, and implementing capability checks. Furthermore, the complete absence of known CVEs and a clean vulnerability history suggest a well-maintained and secure codebase over time.

However, there are a couple of areas that warrant attention. The taint analysis identified two flows with unsanitized paths, which, while not flagged as critical or high severity in this instance, represent a potential risk if not thoroughly investigated and addressed. This indicates a possibility of subtle vulnerabilities that might not be immediately apparent without deeper code inspection. Additionally, the output escaping is not fully robust, with 30% of outputs not being properly escaped, which could lead to cross-site scripting (XSS) vulnerabilities if user-supplied data is involved in these unescaped outputs.

In conclusion, the plugin exhibits many positive security attributes, particularly in its handling of database operations and authentication. The lack of historical vulnerabilities is a significant strength. The primary concerns lie in the identified unsanitized paths and the incomplete output escaping, which, although not currently manifesting as high-severity issues, represent potential attack vectors that should be proactively remediated to maintain a strong security posture.

Key Concerns

  • Taint flows with unsanitized paths
  • Incomplete output escaping
Vulnerabilities
None known

i4a Single Sign-On Security Vulnerabilities

No known vulnerabilities — this is a good sign.
Version History

i4a Single Sign-On Release Timeline

v1.0.4
v1.0.3
v1.0.2
v1.0.1
v1.0.0
Code Analysis
Analyzed Mar 17, 2026

i4a Single Sign-On Code Analysis

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

SQL Query Safety

100% prepared3 total queries

Output Escaping

70% escaped10 total outputs
Data Flows · Security
2 unsanitized

Data Flow Analysis

2 flows2 with unsanitized paths
store (src\WP\Views\Form.php:7)
Source (user input) Sink (dangerous op) Sanitizer Transform Unsanitized Sanitized
Attack Surface

i4a Single Sign-On Attack Surface

Entry Points0
Unprotected0
WordPress Hooks 12
actionwp_logouti4a-single-sign-on.php:45
filterauthenticatesrc\i4aAuth\Authenticate.php:7
filterinitsrc\i4aAuth\AutoLogin.php:7
filterafter_setup_themesrc\i4aAuth\RemoveAdminBar.php:6
actionadmin_menusrc\i4aAuth\RemoveAdminBar.php:7
filtershow_admin_barsrc\i4aAuth\RemoveAdminBar.php:17
filterwp_admin_bar_classsrc\i4aAuth\RemoveAdminBar.php:18
filtershow_password_fieldssrc\i4aAuth\RestrictPassword.php:5
filterallow_password_resetsrc\i4aAuth\RestrictPassword.php:6
filtergettextsrc\i4aAuth\RestrictPassword.php:7
actionadmin_menusrc\WP\Views\Page.php:13
actioni4a_bodysrc\WP\Views\Page.php:23
Maintenance & Trust

i4a Single Sign-On Maintenance & Trust

Maintenance Signals

WordPress version tested6.9.4
Last updatedFeb 2, 2026
PHP min version5.6
Downloads2K

Community Trust

Rating0/100
Number of ratings0
Active installs10
Developer Profile

i4a Single Sign-On Developer Profile

i4awordpress

1 plugin · 10 total installs

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

How We Detect i4a Single Sign-On

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

Asset Fingerprints

Asset Paths
/wp-content/plugins/internet4associations-single-sign-on/src/i4aAuth/Views/internet4associations.js/wp-content/plugins/internet4associations-single-sign-on/src/i4aAuth/Views/internet4associations-help.js/wp-content/plugins/internet4associations-single-sign-on/src/i4aAuth/Views/internet4associations-import.js/wp-content/plugins/internet4associations-single-sign-on/src/i4aAuth/Views/render.js
Script Paths
/wp-content/plugins/internet4associations-single-sign-on/src/i4aAuth/Views/internet4associations.js/wp-content/plugins/internet4associations-single-sign-on/src/i4aAuth/Views/internet4associations-help.js/wp-content/plugins/internet4associations-single-sign-on/src/i4aAuth/Views/internet4associations-import.js/wp-content/plugins/internet4associations-single-sign-on/src/i4aAuth/Views/render.js
Version Parameters
internet4associations-single-sign-on/style.css?ver=internet4associations-single-sign-on/script.js?ver=

HTML / DOM Fingerprints

CSS Classes
i4aImportResultMessage
HTML Comments
<!-- clear_i4a_cookies_on_logout: unset the cookies and force them to expire so they are not continually auto-logged back into the WP site after WP logout request --><!-- import custom i4a roles from i4a to WordPress --><!-- Example Code: add_role('i4a_membertypename', 'i4a: Member Type Name', array()); --><!-- if the user is not a "current" member, then remove their "subscriber" role and add the role of "i4a: Non-Member" to their user record in WP -->+1 more
JS Globals
i4a_getCookieRootDomain
FAQ

Frequently Asked Questions about i4a Single Sign-On