Simple Force SSL Security & Risk Analysis

wordpress.org/plugins/simple-force-ssl

This plugin forces all traffic to be redirected to the HTTPS version of your site using a 301 redirect.

300 active installs v2.0 PHP 5.6+ WP 3.0+ Updated Dec 6, 2024
force-redirecthttpsredirectsecure-connectionssl
92
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is Simple Force SSL Safe to Use in 2026?

Generally Safe

Score 92/100

Simple Force SSL has no known CVEs and is actively maintained. It's a solid choice for most WordPress installations.

No known CVEs Updated 1yr ago
Risk Assessment

The "simple-force-ssl" v2.0 plugin exhibits a generally strong security posture based on the provided static analysis. The absence of AJAX handlers, REST API routes, shortcodes, and cron events, combined with 100% of SQL queries using prepared statements and the presence of nonce checks, significantly limits the potential attack surface. The plugin also has no recorded vulnerability history, suggesting a commitment to secure development practices and prompt patching if issues arise.

However, a critical concern emerges from the taint analysis, which identified one flow with unsanitized paths. While no critical or high severity taint flows were reported, this single unsanitized path represents a potential risk, especially if it involves user-supplied input that is not properly validated or escaped before being used. Furthermore, the static analysis flagged one total output that is not properly escaped, which could lead to cross-site scripting (XSS) vulnerabilities if that output contains untrusted data.

In conclusion, the plugin's strengths lie in its minimal attack surface and diligent use of prepared statements for SQL. The vulnerability history is also a positive indicator. Nevertheless, the presence of an unsanitized path and unescaped output requires attention. Addressing these specific code-level concerns will further enhance the plugin's security.

Key Concerns

  • Flow with unsanitized path
  • Unescaped output found
Vulnerabilities
None known

Simple Force SSL Security Vulnerabilities

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

Simple Force SSL Release Timeline

v2.0Current
Code Analysis
Analyzed Mar 16, 2026

Simple Force SSL Code Analysis

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

Output Escaping

0% escaped1 total outputs
Data Flows · Security
1 unsanitized

Data Flow Analysis

3 flows1 with unsanitized paths
me_simple_force_ssl (simple-force-ssl.php:38)
Source (user input) Sink (dangerous op) Sanitizer Transform Unsanitized Sanitized
Attack Surface

Simple Force SSL Attack Surface

Entry Points0
Unprotected0
WordPress Hooks 2
actiontemplate_redirectsimple-force-ssl.php:46
actionadmin_menusimple-force-ssl.php:70
Maintenance & Trust

Simple Force SSL Maintenance & Trust

Maintenance Signals

WordPress version tested6.7.5
Last updatedDec 6, 2024
PHP min version5.6
Downloads7K

Community Trust

Rating0/100
Number of ratings0
Active installs300
Developer Profile

Simple Force SSL Developer Profile

imemine

6 plugins · 10K total installs

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

How We Detect Simple Force SSL

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

Asset Fingerprints

HTML / DOM Fingerprints

Data Attributes
name="me_simple_force_ssl_enabled"name="me_simple_force_ssl_save"
FAQ

Frequently Asked Questions about Simple Force SSL