WpCrypt Security & Risk Analysis

wordpress.org/plugins/wpcrypt

Allow users to change password encryption method to SHA1, SHA2, AES Rijndael and more...

10 active installs v0.1 PHP + WP 3.3+ Updated Apr 16, 2015
encryptionhashhashespasswordsecurity
85
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is WpCrypt Safe to Use in 2026?

Generally Safe

Score 85/100

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

No known CVEs Updated 10yr ago
Risk Assessment

The "wpcrypt" v0.1 plugin exhibits a mixed security posture. On the positive side, there are no known CVEs, no critical or high severity taint flows, no dangerous functions, and all SQL queries utilize prepared statements. The attack surface is also reported as zero, and there are no external HTTP requests or file operations, which are generally good signs. However, a significant concern is that 100% of the identified output operations are not properly escaped. This could lead to cross-site scripting (XSS) vulnerabilities if user-supplied data is outputted directly without sanitization. Additionally, the plugin has zero nonce checks, which, while not explicitly tied to an attack vector in this analysis, is a fundamental security practice for many WordPress interactions, especially if any entry points are discovered later or if functionality relies on state changes. The vulnerability history being clean is a positive indicator, but the lack of proper output escaping represents a clear and present risk that needs immediate attention.

Key Concerns

  • Output not properly escaped
  • No nonce checks
Vulnerabilities
None known

WpCrypt Security Vulnerabilities

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

WpCrypt Code Analysis

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

SQL Query Safety

100% prepared2 total queries

Output Escaping

0% escaped6 total outputs
Data Flows
All sanitized

Data Flow Analysis

2 flows
save_extra_user_profile_fields (wpcrypt-core.php:74)
Source (user input) Sink (dangerous op) Sanitizer Transform Unsanitized Sanitized
Attack Surface

WpCrypt Attack Surface

Entry Points0
Unprotected0
WordPress Hooks 8
actioninitwp-crypt.php:53
actionadmin_noticeswp-crypt.php:86
actionshow_user_profilewp-crypt.php:88
actionedit_user_profilewp-crypt.php:89
actionpersonal_options_updatewp-crypt.php:91
actionedit_user_profile_updatewp-crypt.php:92
filterhash_passwordwp-crypt.php:95
filtercheck_passwordwp-crypt.php:96
Maintenance & Trust

WpCrypt Maintenance & Trust

Maintenance Signals

WordPress version tested3.5.2
Last updatedApr 16, 2015
PHP min version
Downloads3K

Community Trust

Rating100/100
Number of ratings1
Active installs10
Developer Profile

WpCrypt Developer Profile

bruno.sousa

2 plugins · 20 total installs

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

How We Detect WpCrypt

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

Asset Fingerprints

Asset Paths
/wp-content/plugins/wpcrypt/css/admin.css/wp-content/plugins/wpcrypt/js/admin.js
Script Paths
/wp-content/plugins/wpcrypt/js/admin.js
Version Parameters
wpcrypt-admin-scriptwpcrypt-admin-style

HTML / DOM Fingerprints

HTML Comments
<!-- TODO: Define custom functionality for your plugin here --><!-- For more information: --><!-- http://codex.wordpress.org/Plugin_API#Hooks.2C_Actions_and_Filters -->
Data Attributes
id="wpcrypt_method"id="cryptPass"id="AES_key"
Shortcode Output
<h3 id='wordpress-seo'>WpCrypt Options</h3>
FAQ

Frequently Asked Questions about WpCrypt