LH HSTS Security & Risk Analysis

wordpress.org/plugins/lh-hsts

HSTS is HTTP Strict Transport Security, a means to enforce using SSL even if the user accesses the site through HTTP and not HTTPS.

700 active installs v1.25 PHP + WP 3.0+ Updated Jul 12, 2020
hstshttpsredirectsecurityssl
85
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is LH HSTS Safe to Use in 2026?

Generally Safe

Score 85/100

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

No known CVEs Updated 5yr ago
Risk Assessment

The lh-hsts plugin v1.25 exhibits a very strong security posture based on the provided static analysis and vulnerability history. The absence of any detected dangerous functions, raw SQL queries, unescaped outputs, file operations, external HTTP requests, or nonce/capability checks is highly commendable. The plugin appears to have a minimal attack surface, with no identified AJAX handlers, REST API routes, shortcodes, or cron events. This indicates a well-written and secure plugin architecture that adheres to best practices for WordPress development.

While the overall security is excellent, the taint analysis reveals two flows with unsanitized paths. Although no critical or high severity issues were found in these flows, the presence of unsanitized paths, even if not leading to immediate exploitable vulnerabilities in this specific version, warrants attention. It suggests a potential area for improvement to ensure absolute data sanitization, even in the absence of clear exploit vectors in the current analysis.

The plugin's vulnerability history is completely clean, with no known CVEs, which further reinforces its secure reputation. This lack of past vulnerabilities suggests consistent development quality and responsible maintenance. In conclusion, lh-hsts v1.25 is an exceptionally secure plugin, with the only minor concern being the two identified unsanitized paths in the taint analysis, which do not currently present a significant risk due to the absence of exploitable code signals.

Key Concerns

  • Flows with unsanitized paths
Vulnerabilities
None known

LH HSTS Security Vulnerabilities

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

LH HSTS Code Analysis

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

Data Flow Analysis

2 flows2 with unsanitized paths
add_header (lh-hsts.php:68)
Source (user input) Sink (dangerous op) Sanitizer Transform Unsanitized Sanitized
Attack Surface

LH HSTS Attack Surface

Entry Points0
Unprotected0
WordPress Hooks 5
filterlh_hsts_subdomainlh-hsts.php:40
filterlh_hsts_preloadlh-hsts.php:41
filterlh_hsts_redirectlh-hsts.php:42
filterlh_hsts_max_agelh-hsts.php:43
actionsend_headerslh-hsts.php:49
Maintenance & Trust

LH HSTS Maintenance & Trust

Maintenance Signals

WordPress version tested5.4.19
Last updatedJul 12, 2020
PHP min version
Downloads350K

Community Trust

Rating78/100
Number of ratings7
Active installs700
Developer Profile

LH HSTS 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 HSTS

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 HSTS