Finding admin users you did not create in your WordPress dashboard is a clear sign your site has been compromised. Hackers create admin accounts to maintain persistent access even after the initial breach vector is closed.
Most common causes we diagnose:
Systematic, fast, and safe process:
Delete all admin users you did not create. Also check for editor and author roles with suspicious email addresses.
Immediately reset passwords for all legitimate admin accounts using strong, unique passwords with 2FA if possible.
Check server logs for the REST API endpoint, xmlrpc.php calls, or SQL injection that created the unauthorized accounts, then block that entry point.
Our WordPress expert responds in minutes.
Several ways: exploiting unauthenticated REST API endpoints in old WordPress versions, using SQL injection, exploiting xmlrpc.php, or using a password reset token obtained via email compromise.
No — the unknown admin is a symptom, not the cause. You must also find and close the security vulnerability that allowed the account to be created, otherwise new ones will appear.
Three main ways: an attacker exploited a plugin vulnerability (REST API, auth bypass) to call wp_insert_user; an attacker stole credentials and created the user manually; or a backdoor file silently calls user creation functions on demand.
Removing the user is necessary but NOT sufficient. The vulnerability that allowed creation is still there. Without closing the entry point, the attacker creates a new admin within hours. Full hardening is required.
Check: WordPress activity log plugins (Stream, WP Activity Log), wp_users registration date, recently modified theme/plugin files, new posts/pages, modified .htaccess. We do a comprehensive forensics audit.
Yes. WordPress admin users have access to all user data (emails, addresses), order data, and any data plugins store. Assume sensitive data exposure when unknown admin existed for any duration.
Partly. It cuts off any access via stolen passwords. But if the entry point is a plugin vulnerability or backdoor file, attackers create new admins without needing passwords. We close the actual vulnerability.
wp_users.user_registered shows the timestamp. user_meta wp_capabilities shows when admin role was assigned. Server access logs around that time show the IP and user-agent of the request that created the user.
Yes. Common attacker tactics: names like 'wpsupport', 'admin2', 'backup', 'wp-admin', or your real name slightly modified. We compare against a baseline of known users you confirm.
Only if you have a security plugin or custom code for it. Default WordPress doesn't send admin creation notifications. We install monitoring that emails you instantly when any admin user is created.
Limited without a pre-installed activity log. We can check: file modification timestamps within the user's active period, post/page audit logs (if WP Stream or similar was active), and wp_usermeta for tracked actions.
Yes — best practice. Send a security notification: brief description of the incident, what data may have been accessed, what you've done to fix it, and any recommended actions (password change, etc.). Transparency rebuilds trust.
Yes. SQL injection attacks can directly INSERT into wp_users and wp_usermeta tables, bypassing PHP entirely. We check for unusual database access patterns and lock down DB user permissions.
No. Users live in the database, not in core files. Reinstalling core only updates wp-includes/wp-admin/index.php files. We remove unknown users via the wp_users table directly with WP-CLI or SQL.
Five layers: 1) keep all plugins/themes updated, 2) install a WAF blocking REST API user creation from non-authenticated requests, 3) limit /wp-login.php to known IPs, 4) require 2FA for all admins, 5) enable activity log monitoring for instant alerts.
WordPress site hacked? We clean it, close the backdoor, and secure it — same day.
Response in minutes. No data loss. No diagnosis charge.
wpfix.blimx.com