Forgotten accounts belonging to former employees, contractors, or vendors add unnecessary access paths to your administration. To strengthen the security of inactive WordPress accounts, don’t delete users at random. Start by determining who still uses each access, what it permits, and what would happen to any associated content.
This check doesn’t replace updates, backups, or protection against login attempts. However, it reduces privileges that are no longer needed. OWASP recommends auditing accounts and disabling unused accounts in its access controls.
Why deal with old access
An account doesn’t need to be used every week to remain legitimate. For example, an accountant may check the site at certain times. Likewise, a vendor may need occasional access for a scheduled task.
By contrast, credentials linked to someone who no longer works with you shouldn’t remain active by default. The risk depends mainly on the rights granted. a former administrator can change plugins, settings, accounts, and content.
Even a more limited role deserves a clear decision. It still permits a login and may grant access to important site functions. Before the audit, check what each role actually allows. The article Understanding roles and permissions in WordPress helps distinguish a real need from rights granted by habit.
Inventorying users
In the admin, open Users, then review the full list. This screen shows the username, name, email address, role, and number of posts associated. It also allows you to search for, edit, and delete users.
See the WordPress Users screen documentation before performing a bulk action. It also explains the options offered when you delete an account.
Don’t confuse lack of posts with lack of access. A technical administrator may not have written any articles. Conversely, an inactive author may own content you need to keep.
Create a decision list
Copy useful information into a tracking table accessible only to authorized people. Do not record passwords or technical secrets there. The goal is to make each decision verifiable.
- Username and associated email address.
- Name of the person or company that owns the account.
- Current role and operational reason for the access.
- Last known task or associated contract.
- Content attributed to the account, if any.
- Decision made, responsible party, and review date.
Then group accounts by risk level. Start with administrators, generic accounts, former vendor addresses, and accounts without a confirmed owner. This will reduce the most sensitive access without treating the entire directory the same way.
Confirm the need before modifying an account
Before making any change, confirm the account’s status with the person responsible for the site or contract. Use an already known communication channel. Don’t rely solely on the address configured in the profile if you don’t know who now controls that email inbox.
Ask three simple questions: does the person still have an active mandate, what work must they accomplish, and what is the minimal role required? This approach applies the principle of least privilege without assuming a former account is malicious.
Also pay special attention to shared accounts. When your organization allows it, replace them with named accounts. You can then tie each access to a person and remove it at the end of the relevant mandate.
Choose the appropriate action
After validation, choose an action appropriate to the account. Avoid keeping administrative access simply because it might be useful someday. However, check content, integrations, and dependencies before deleting a user.
Keep the account with reduced rights
Keep the account if its owner has a real, current need. Still, reduce its role to the minimum necessary when their responsibilities have changed. WordPress allows you to change the role of multiple users from the Users screen.
A role groups the capabilities that determine the privileges available in the admin. The official roles and capabilities documentation describes this relationship. Note the new role, the reason for retention, and the next review date.
Revoke integration accesses
A departure doesn’t always concern logging in via a browser. Also check application passwords used by a script, a mobile app, or a third‑party service. These credentials are tied to a WordPress account and can be revoked separately.
The documentation on application passwords states that they also include usage data, including last used and last IP address. This information can help identify an integration that’s still active.
Revoke only the identifier associated with the service that’s no longer needed. If an automation remains necessary, first confirm its owner, role, and planned replacement. You can also consult this guide on safely using WordPress application passwords.
Delete an account after verification
Delete the account when there is no longer a need to retain it. Before confirming, check the posts and links associated with that user. WordPress lets you either delete that content or assign it to another user.
The technical reference for deleting a user details the consequences of this action, including the possible reassignment of content. Choose a durable owner, such as an editorial account controlled by your organization. Avoid assigning posts to a personal account that might disappear later.
On a multisite network, carefully check the scope of the action. Depending on the context, removing a user from a site does not have the same result as deleting their account across the whole network.
Keep a record and repeat the audit
After each change, update your decision table. Record at minimum the date, the account processed, the action taken, the content reassigned, and the person who authorized the change. This record makes future checks easier and prevents recreating access without understanding why it was removed.
Schedule a periodic review, for example during your regular check‑in or after an employee leaves. Also integrate this check into your onboarding and offboarding process: create a named access, assign the minimal role, confirm the owner, then remove or review the access at the end of the mandate.
Finally, monitor other signals that can accompany an undesirable access. The monitoring of WordPress file changes usefully complements the user audit. It helps spot technical changes that require validation.
Managing inactive WordPress accounts becomes easier when each access has an owner, a clear reason, limited permissions, and a review date.









