Change Username Security & Risk Analysis

wordpress.org/plugins/change-username

Change usernames of your WordPress users effectively.

4K active installs v1.0.2 PHP 7.2+ WP 4.1+ Updated Oct 4, 2024
change-loginchange-usernameloginusername
92
A · Safe
CVEs total0
Unpatched0
Last CVENever
Download
Safety Verdict

Is Change Username Safe to Use in 2026?

Generally Safe

Score 92/100

Change Username 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 'change-username' plugin v1.0.2 exhibits a generally good security posture in several key areas. The absence of dangerous functions, the exclusive use of prepared statements for all SQL queries, and the fact that all output is properly escaped are strong indicators of secure coding practices. Furthermore, the plugin demonstrates the use of nonces and capability checks, which are essential for WordPress security. The vulnerability history being completely clear also suggests a well-maintained and previously secure codebase.

However, a significant concern arises from the static analysis revealing one unprotected AJAX handler. With a total of one entry point and one unprotected entry point, this constitutes 100% of the attack surface being exposed without proper authentication or authorization checks. While taint analysis did not reveal any issues with unsanitized paths, the presence of an unprotected AJAX endpoint is a direct gateway for potential abuse if the functionality it exposes can be manipulated by an unauthenticated user.

In conclusion, while the plugin has commendable strengths in its data handling and output sanitization, the single unprotected AJAX handler presents a clear and direct security risk. Addressing this vulnerability should be the highest priority to improve the plugin's overall security.

Key Concerns

  • Unprotected AJAX handler
Vulnerabilities
None known

Change Username Security Vulnerabilities

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

Change Username Release Timeline

v1.0.2Current
v1.0.1
v1.0
Code Analysis
Analyzed Mar 16, 2026

Change Username Code Analysis

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

SQL Query Safety

100% prepared6 total queries
Data Flows · Security
All sanitized

Data Flow Analysis

2 flows
ajax_handler (src\functions.php:29)
Source (user input) Sink (dangerous op) Sanitizer Transform Unsanitized Sanitized
Attack Surface
1 unprotected

Change Username Attack Surface

Entry Points1
Unprotected1

AJAX Handlers 1

authwp_ajax_change_usernamechange-username.php:40
WordPress Hooks 2
actionadmin_enqueue_scriptschange-username.php:39
actionplugins_loadedchange-username.php:43
Maintenance & Trust

Change Username Maintenance & Trust

Maintenance Signals

WordPress version tested6.6.5
Last updatedOct 4, 2024
PHP min version7.2
Downloads27K

Community Trust

Rating88/100
Number of ratings5
Active installs4K
Developer Profile

Change Username Developer Profile

Danny van Kooten

9 plugins · 1.1M total installs

77
trust score
Avg Security Score
97/100
Avg Patch Time
708 days
View full developer profile
Detection Fingerprints

How We Detect Change Username

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

Asset Fingerprints

Asset Paths
/wp-content/plugins/change-username/assets/js/script.min.js
Script Paths
/wp-content/plugins/change-username/assets/js/script.min.js
Version Parameters
change-username/assets/js/script.min.js?ver=

HTML / DOM Fingerprints

JS Globals
change_username
FAQ

Frequently Asked Questions about Change Username