NoSSL – protect your website Security & Risk Analysis

wordpress.org/plugins/nossl-protect-your-website

NoSSL encrypts the logins and all forms of your WordPress.

10 active installs v1.1 PHP + WP 3.0.1+ Updated Sep 21, 2014
none
85
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is NoSSL – protect your website Safe to Use in 2026?

Generally Safe

Score 85/100

NoSSL – protect your website has no known CVEs and is actively maintained. It's a solid choice for most WordPress installations.

No known CVEs Updated 11yr ago
Risk Assessment

The 'nossl-protect-your-website' plugin v1.1 exhibits a mixed security posture. On the positive side, it demonstrates no known CVEs, a clean vulnerability history, and no external HTTP requests, indicating a generally stable and low-profile plugin. The absence of AJAX handlers, REST API routes, shortcodes, and cron events, coupled with the fact that all SQL queries use prepared statements, significantly limits its attack surface and direct database manipulation risks.

However, the static analysis reveals several concerning code signals. The presence of dangerous functions like `set_time_limit`, `unserialize`, `ini_set`, and `create_function` without any apparent authorization or capability checks presents potential risks. `unserialize` is particularly concerning as it can lead to Remote Code Execution (RCE) if used with untrusted input. The low percentage of properly escaped output (9%) suggests a high risk of Cross-Site Scripting (XSS) vulnerabilities, where malicious scripts could be injected and executed in the user's browser.

While the plugin has a clean vulnerability history, this can be misleading. The lack of detected issues might stem from a lack of in-depth analysis or testing rather than inherent security. The combination of dangerous functions and poor output sanitization, without any nonce or capability checks, creates a significant potential for exploitation. Therefore, despite its clean history, the plugin has inherent risks that require attention.

Key Concerns

  • Dangerous function: unserialize without checks
  • Dangerous function: create_function without checks
  • Dangerous function: ini_set without checks
  • Dangerous function: set_time_limit without checks
  • Low percentage of properly escaped output
  • No nonce checks
  • No capability checks
Vulnerabilities
None known

NoSSL – protect your website Security Vulnerabilities

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

NoSSL – protect your website Release Timeline

No version history available.
Code Analysis
Analyzed Apr 16, 2026

NoSSL – protect your website Code Analysis

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

Dangerous Functions Found

set_time_limitset_time_limit (600); //Important: Time limit in seconds, else the script may time out with big keysnossl/generate-new-keypair.php:65
unserializeextract(unserialize($partial));nossl/phpseclib/Crypt/RSA.php:565
ini_setini_set('session.use_cookies', 0);nossl/phpseclib/Crypt/Random.php:143
ini_setini_set('session.use_cookies', $old_use_cookies);nossl/phpseclib/Crypt/Random.php:167
create_functionreturn create_function('$_action, &$self, $_text', $init_crypt . 'if ($_action == "encrypt") { ' . $nossl/phpseclib/Crypt/not_in_use/Base.php:1963

Output Escaping

9% escaped11 total outputs
Attack Surface

NoSSL – protect your website Attack Surface

Entry Points0
Unprotected0
WordPress Hooks 3
actioninitnossl.php:50
actionwp_enqueue_scriptsnossl.php:51
actionlogin_enqueue_scriptsnossl.php:52
Maintenance & Trust

NoSSL – protect your website Maintenance & Trust

Maintenance Signals

WordPress version tested3.4.2
Last updatedSep 21, 2014
PHP min version
Downloads1K

Community Trust

Rating0/100
Number of ratings0
Active installs10
Developer Profile

NoSSL – protect your website Developer Profile

smartinmedia

1 plugin · 10 total installs

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

How We Detect NoSSL – protect your website

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

Asset Fingerprints

Asset Paths
/wp-content/plugins/nossl-protect-your-website/nossl/style/nossl.css/wp-content/plugins/nossl-protect-your-website/nossl/javascript/nossl_start.min.js
Script Paths
/wp-content/plugins/nossl-protect-your-website/nossl/javascript/nossl_start.min.js
Version Parameters
nossl-style?ver=nossl-js?ver=

HTML / DOM Fingerprints

HTML Comments
########################################################################################## NoSSL V1.1 - Encryption between browser and server########################################################################################## Copyright (C) 2013 - 2014 Smart In Media GmbH & Co. KG+6 more
FAQ

Frequently Asked Questions about NoSSL – protect your website