HTTP Authentication By KIMoFy Security & Risk Analysis

wordpress.org/plugins/http-authentication-by-kimofy

HTTP Authentication lets you make a site without letting anyone view it without valid credentials. This can protect the full site or only admin pages.

20 active installs v5.1 PHP + WP 3.5+ Updated Jun 12, 2017
authauthenticationhttp-authhttp-authenticationrestrict-pages
85
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is HTTP Authentication By KIMoFy Safe to Use in 2026?

Generally Safe

Score 85/100

HTTP Authentication By KIMoFy has no known CVEs and is actively maintained. It's a solid choice for most WordPress installations.

No known CVEs Updated 8yr ago
Risk Assessment

Based on the provided static analysis and vulnerability history, the 'http-authentication-by-kimofy' v5.1 plugin exhibits a strong security posture. The absence of any identified AJAX handlers, REST API routes, shortcodes, or cron events with unprotected entry points indicates a minimal attack surface. Furthermore, the code analysis reveals no dangerous functions, file operations, or external HTTP requests, and all SQL queries utilize prepared statements. The vulnerability history is completely clean, with zero recorded CVEs, suggesting a history of secure development practices or a lack of publicly disclosed vulnerabilities.

While the plugin demonstrates good practices in several areas, there is a minor concern regarding output escaping, with 27% of outputs not being properly escaped. Although this does not represent a critical finding in isolation, it is a common vector for cross-site scripting (XSS) vulnerabilities if user-supplied data is involved. The lack of nonce and capability checks on the identified entry points is also a notable absence, though with zero entry points, this risk is currently mitigated. Overall, the plugin appears to be secure due to its limited functionality and lack of historical vulnerabilities, but the unescaped output warrants attention.

Key Concerns

  • Percentage of outputs not properly escaped
Vulnerabilities
None known

HTTP Authentication By KIMoFy Security Vulnerabilities

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

HTTP Authentication By KIMoFy Release Timeline

v5.0
Code Analysis
Analyzed Mar 16, 2026

HTTP Authentication By KIMoFy Code Analysis

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

Output Escaping

73% escaped15 total outputs
Attack Surface

HTTP Authentication By KIMoFy Attack Surface

Entry Points0
Unprotected0
WordPress Hooks 2
actionadmin_inithttp-authentication-by-kimofy.php:20
actionadmin_menuhttp-authentication-by-kimofy.php:217
Maintenance & Trust

HTTP Authentication By KIMoFy Maintenance & Trust

Maintenance Signals

WordPress version tested4.8.28
Last updatedJun 12, 2017
PHP min version
Downloads2K

Community Trust

Rating100/100
Number of ratings1
Active installs20
Developer Profile

HTTP Authentication By KIMoFy Developer Profile

KIMoFy

1 plugin · 20 total installs

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

How We Detect HTTP Authentication By KIMoFy

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

Asset Fingerprints

Asset Paths
/wp-content/plugins/http-authentication-by-kimofy/style.css
Version Parameters
http-authentication-by-kimofy/style.css?ver=

HTML / DOM Fingerprints

CSS Classes
http-auth-tablehttp-for
Data Attributes
name="http_auth_username"name="http_auth_password"name="http_auth_apply"name="http_auth_activate"
FAQ

Frequently Asked Questions about HTTP Authentication By KIMoFy