LH Private Content Login Security & Risk Analysis

wordpress.org/plugins/lh-private-content-login

Redirects non-logged users to the login page when they follow a link to a post, page, or cpt which is protected by post status.

300 active installs v1.05 PHP + WP 5.0+ Updated Feb 28, 2024
loginpost-statusprivate-contentredirectionstatus
85
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is LH Private Content Login Safe to Use in 2026?

Generally Safe

Score 85/100

LH Private Content Login has no known CVEs and is actively maintained. It's a solid choice for most WordPress installations.

No known CVEs Updated 2yr ago
Risk Assessment

Based on the provided static analysis and vulnerability history, the 'lh-private-content-login' plugin version 1.05 exhibits a very strong security posture. The absence of any identified vulnerabilities in its history, combined with the results of the static analysis, suggests that the developers have followed sound security practices. The code analysis reveals no dangerous functions, no raw SQL queries, and all output is properly escaped. Furthermore, the plugin has no external HTTP requests or file operations, minimizing potential attack vectors. The lack of a significant attack surface through AJAX handlers, REST API routes, shortcodes, or cron events is also a positive indicator. There are no untrusted data flows identified in the taint analysis. The plugin's clean history and the absence of any detected security weaknesses in the code indicate a low risk of exploitation. However, it's important to note the absence of nonce and capability checks on the entry points, which, while currently not leading to a discovered vulnerability due to the limited attack surface, represents a potential area for improvement should the plugin's functionality expand.

Key Concerns

  • Missing nonce checks on entry points
  • Missing capability checks on entry points
Vulnerabilities
None known

LH Private Content Login Security Vulnerabilities

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

LH Private Content Login Code Analysis

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

SQL Query Safety

100% prepared1 total queries
Attack Surface

LH Private Content Login Attack Surface

Entry Points0
Unprotected0
WordPress Hooks 3
actiontemplate_redirectlh-private-content-login.php:137
filterlogin_messagelh-private-content-login.php:140
actionplugins_loadedlh-private-content-login.php:163
Maintenance & Trust

LH Private Content Login Maintenance & Trust

Maintenance Signals

WordPress version tested6.4.8
Last updatedFeb 28, 2024
PHP min version
Downloads6K

Community Trust

Rating100/100
Number of ratings5
Active installs300
Developer Profile

LH Private Content Login Developer Profile

shawfactor

77 plugins · 15K total installs

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

How We Detect LH Private Content Login

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

Asset Fingerprints

HTML / DOM Fingerprints

FAQ

Frequently Asked Questions about LH Private Content Login