Authenticator Security & Risk Analysis

wordpress.org/plugins/authenticator

This plugin allows you to make your WordPress site accessible to logged in users only.

1K active installs v1.3.1 PHP 5.6+ WP 5.0+ Updated Jan 21, 2026
accessaccessibleauthentificationloginmembers
99
A · Safe
CVEs total1
Unpatched0
Last CVENov 26, 2022
Safety Verdict

Is Authenticator Safe to Use in 2026?

Generally Safe

Score 99/100

Authenticator has a strong security track record. Known vulnerabilities have been patched promptly.

1 known CVELast CVE: Nov 26, 2022Updated 2mo ago
Risk Assessment

The Authenticator plugin v1.3.1 exhibits a mixed security posture. While it has a small attack surface and implements a reasonable number of capability checks and a nonce check, there are significant concerns stemming from its code analysis and vulnerability history. The static analysis reveals that 100% of its SQL queries are not using prepared statements, which is a critical vulnerability vector for SQL injection. Furthermore, a concerning 71% of analyzed taint flows have unsanitized paths, indicating potential for insecure data handling and path traversal issues, although no critical or high severity taint flows were specifically identified in this scan. The vulnerability history highlights a past high-severity vulnerability related to missing authorization, which is a common and dangerous class of flaws. The fact that this high-severity vulnerability is now patched is positive, but the historical pattern of such issues warrants caution. Overall, the plugin has strengths in limiting its direct attack surface, but the lack of prepared statements for SQL and the past authorization issues suggest that careful review and potential remediation are necessary to improve its security.

Key Concerns

  • 100% of SQL queries are not prepared
  • 5 out of 7 taint flows have unsanitized paths
  • Past high severity vulnerability (missing authorization)
  • Only 20% of outputs are properly escaped
Vulnerabilities
1

Authenticator Security Vulnerabilities

CVEs by Year

1 CVE in 2022
2022
Patched Has unpatched

Severity Breakdown

High
1

1 total CVE

CVE-2022-3994high · 8.1Missing Authorization

Authenticator <= 1.3.0 - Missing Authorization

Nov 26, 2022 Patched in 1.3.1 (423d)
Code Analysis
Analyzed Mar 16, 2026

Authenticator Code Analysis

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

SQL Query Safety

0% prepared1 total queries

Output Escaping

20% escaped20 total outputs
Data Flows
5 unsanitized

Data Flow Analysis

7 flows5 with unsanitized paths
_exit_403 (authenticator.php:442)
Source (user input) Sink (dangerous op) Sanitizer Transform Unsanitized Sanitized
Attack Surface

Authenticator Attack Surface

Entry Points1
Unprotected0

AJAX Handlers 1

authwp_ajax_regenerate_tokeninc\class-Authenticator_Settings_UI.php:29
WordPress Hooks 16
actionplugins_loadedauthenticator.php:23
actiontemplate_redirectauthenticator.php:153
actionadmin_initauthenticator.php:155
filterauth_cookie_expirationauthenticator.php:159
actionadmin_initauthenticator.php:161
filterauthenticator_get_optionsauthenticator.php:162
actioninitauthenticator.php:165
actioninitauthenticator.php:166
actioninitauthenticator.php:167
actionlogin_footerauthenticator.php:169
filterxmlrpc_enabledauthenticator.php:385
actionrest_authentication_errorsauthenticator.php:399
actioninitinc\class-Authenticator_Protect_Upload.php:16
actionadmin_enqueue_scriptsinc\class-Authenticator_Settings_UI.php:28
actionshow_user_profileinc\class-Authenticator_User_Profile.php:21
actionedit_user_profileinc\class-Authenticator_User_Profile.php:22
Maintenance & Trust

Authenticator Maintenance & Trust

Maintenance Signals

WordPress version tested6.9.4
Last updatedJan 21, 2026
PHP min version5.6
Downloads98K

Community Trust

Rating100/100
Number of ratings8
Active installs1K
Developer Profile

Authenticator Developer Profile

Syde GmbH (formerly Inpsyde)

3 plugins · 2K total installs

73
trust score
Avg Security Score
92/100
Avg Patch Time
423 days
View full developer profile
Detection Fingerprints

How We Detect Authenticator

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

Asset Fingerprints

Asset Paths
/wp-content/plugins/authenticator/css/admin.css/wp-content/plugins/authenticator/css/admin-layout.css/wp-content/plugins/authenticator/css/settings.css/wp-content/plugins/authenticator/js/admin.js
Script Paths
/wp-content/plugins/authenticator/js/admin.js
Version Parameters
authenticator/css/admin.css?ver=authenticator/css/admin-layout.css?ver=authenticator/css/settings.css?ver=authenticator/js/admin.js?ver=

HTML / DOM Fingerprints

CSS Classes
authenticator-settings-wrap
HTML Comments
BEGIN: Authenticator PluginEND: Authenticator Plugin
Data Attributes
data-authenticator-nonce
JS Globals
authenticator_admin_params
REST Endpoints
/wp-json/authenticator/v1/settings
FAQ

Frequently Asked Questions about Authenticator