Token Access Security & Risk Analysis

wordpress.org/plugins/token-access

Limit access to the site to those with a cookie token. Visitors without the cookie see a customisable "coming soon" style of page.

10 active installs v1.8.2 PHP 7.4+ WP 6.0+ Updated Jul 3, 2025
accesscookieprivatepublicwhitelist
100
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is Token Access Safe to Use in 2026?

Generally Safe

Score 100/100

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

No known CVEs Updated 9mo ago
Risk Assessment

The "token-access" plugin v1.8.2 demonstrates a generally good security posture with no recorded vulnerabilities and a clean static analysis report in several key areas. The absence of known CVEs and a lack of critical or high severity taint flows is highly positive. Furthermore, the plugin utilizes prepared statements for all SQL queries, indicating robust protection against SQL injection. However, the static analysis does reveal a couple of areas that warrant attention. The presence of file operations without explicit security checks could be a concern depending on the nature of these operations. Additionally, the report shows that 17% of output is not properly escaped, which could lead to Cross-Site Scripting (XSS) vulnerabilities if user-supplied data is involved in these outputs. The lack of capability checks and nonce checks on any potential entry points, while currently showing zero entry points, means that if new entry points are introduced in future updates, they might be unprotected. Overall, while the plugin has a strong foundation, these specific areas require further scrutiny to ensure complete security.

Key Concerns

  • Unescaped output detected
  • File operations detected without clear security context
  • No capability checks on entry points
  • No nonce checks on entry points
Vulnerabilities
None known

Token Access Security Vulnerabilities

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

Token Access Code Analysis

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

Output Escaping

83% escaped12 total outputs
Data Flows
2 unsanitized

Data Flow Analysis

2 flows2 with unsanitized paths
hijack_public_pages (includes\class-token-access-public.php:21)
Source (user input) Sink (dangerous op) Sanitizer Transform Unsanitized Sanitized
Attack Surface

Token Access Attack Surface

Entry Points0
Unprotected0
WordPress Hooks 4
actionadmin_initincludes\class-token-access-admin.php:15
actioninitincludes\class-token-access-public.php:14
actionwp_footerincludes\class-token-access-public.php:60
actioninitindex.php:43
Maintenance & Trust

Token Access Maintenance & Trust

Maintenance Signals

WordPress version tested6.6.5
Last updatedJul 3, 2025
PHP min version7.4
Downloads6K

Community Trust

Rating100/100
Number of ratings2
Active installs10
Developer Profile

Token Access Developer Profile

Anthony

5 plugins · 270 total installs

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

How We Detect Token Access

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

Asset Fingerprints

Asset Paths
/wp-content/plugins/token-access/assets/css/token-access.css/wp-content/plugins/token-access/assets/js/token-access.js
Script Paths
/wp-content/plugins/token-access/assets/js/token-access.js
Version Parameters
token-access.css?ver=token-access.js?ver=

HTML / DOM Fingerprints

CSS Classes
token-access-placeholder-content
HTML Comments
<!-- Token Access Placeholder --><!-- End Token Access Placeholder -->
Data Attributes
data-token-access-token-keydata-token-access-expiry-hoursdata-token-access-remove-token-urldata-token-access-add-token-url
JS Globals
tokenAccessSettings
FAQ

Frequently Asked Questions about Token Access