Enforce Strong Password Security & Risk Analysis

wordpress.org/plugins/enforce-strong-password

Forces all users to have a strong password when they're changing it on their profile page.

100 active installs v1.3.5 PHP + WP 3.5.1+ Updated May 13, 2013
enforceforcepasswordstrong
85
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is Enforce Strong Password Safe to Use in 2026?

Generally Safe

Score 85/100

Enforce Strong Password has no known CVEs and is actively maintained. It's a solid choice for most WordPress installations.

No known CVEs Updated 12yr ago
Risk Assessment

The "enforce-strong-password" plugin v1.3.5 exhibits a generally positive security posture based on the static analysis provided. There are no identified entry points that are unprotected, and the plugin does not utilize dangerous functions, perform file operations, or make external HTTP requests. The use of prepared statements for all SQL queries is a significant strength, mitigating risks of SQL injection. The lack of any recorded vulnerabilities in its history also suggests a history of secure development or diligent patching.

However, a critical concern emerges from the static analysis regarding output escaping. With 4 total outputs and 0% properly escaped, this indicates a high risk of Cross-Site Scripting (XSS) vulnerabilities. Any user-supplied data or dynamically generated content that is outputted by this plugin without proper sanitization could be exploited by attackers to inject malicious scripts into the website, potentially leading to session hijacking, defacement, or redirection to malicious sites.

While the plugin's attack surface is zero and it has no recorded CVEs, the complete absence of output escaping is a serious deficiency. This suggests a need for immediate review and remediation of all output mechanisms within the plugin to ensure proper sanitization before rendering any data. The plugin's strengths in other areas are overshadowed by this critical oversight, making it a moderate risk if not addressed.

Key Concerns

  • All outputs unescaped
Vulnerabilities
None known

Enforce Strong Password Security Vulnerabilities

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

Enforce Strong Password Code Analysis

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

Output Escaping

0% escaped4 total outputs
Attack Surface

Enforce Strong Password Attack Surface

Entry Points0
Unprotected0
WordPress Hooks 5
actioninitenforce-strong-password.php:41
actionuser_profile_update_errorsenforce-strong-password.php:42
actionadmin_menuenforce-strong-password.php:43
actionnetwork_admin_menuenforce-strong-password.php:44
actionvalidate_password_resetenforce-strong-password.php:45
Maintenance & Trust

Enforce Strong Password Maintenance & Trust

Maintenance Signals

WordPress version tested3.5.2
Last updatedMay 13, 2013
PHP min version
Downloads8K

Community Trust

Rating80/100
Number of ratings1
Active installs100
Developer Profile

Enforce Strong Password Developer Profile

Jan Štětina

8 plugins · 200 total installs

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

How We Detect Enforce Strong Password

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

Asset Fingerprints

Asset Paths
/wp-content/plugins/enforce-strong-password/languages

HTML / DOM Fingerprints

CSS Classes
zan-nag
HTML Comments
source: http://sltaylor.co.uk/blog/enforce-strong-wordpress-passwords/Copyright (c) Zaantar (email: zaantar@gmail.com)This program is free software; you can redistribute it and/or modifyit under the terms of the GNU General Public License, version 2, as+8 more
Data Attributes
name="settings[hide_donation_button]"
FAQ

Frequently Asked Questions about Enforce Strong Password