How to Change Joomla Credentials After a Security Incident

After a Joomla security incident, change more than the Joomla login password. Rotate every credential or token the attacker could have reached, do it from a trusted device, revoke old access, and verify that the underlying compromise has been removed.

Contain first and rotate from a clean device

Restrict the compromised site and preserve evidence before changing credentials. Perform credential changes from a workstation you trust; otherwise malware or a stolen browser session can capture the new secrets immediately.

Rotate hosting and server access

Change hosting control-panel passwords, SSH/SFTP or FTP credentials, deployment keys, and any account capable of modifying the site. Remove obsolete accounts and revoke old keys. A Joomla password reset cannot protect the site while an attacker still has server-level write access.

Rotate the database credential safely

Set a new database password through the hosting or database administration system, then update Joomla's database password in configuration.php. Test the frontend and Administrator immediately. Do not expose the new password in tickets, screenshots, shell history, or shared documents.

Reset privileged Joomla accounts

In Users → Manage, identify every Administrator and Super User. Reset passwords for legitimate administrators and block accounts that cannot be verified. Review group membership and email addresses as well as passwords, because an attacker may have changed privileges on an existing account.

Rotate integration secrets and invalidate old access

Change exposed SMTP, payment, storage, API, backup, CDN, webhook, and other integration credentials. Revoke active sessions, API tokens, app passwords, SSH keys, remembered devices, and recovery codes where supported. Re-enroll MFA or WebAuthn factors if their integrity is uncertain.

Verify that rotation actually removed access

Test legitimate logins and integrations after rotation, then monitor authentication and access logs for attempts using old credentials. Credential rotation must accompany removal of malicious files, vulnerable extensions, unauthorized users, and persistence; otherwise the attacker can simply steal the new credentials again.


Need More Help with Joomla?

Still having trouble? Open a support ticket with QuantaCade Support and we'll be happy to help where we can.

Support priority is given to QuantaCade products, services, and customers. However, we're also happy to assist fellow Joomla users with general Joomla questions and troubleshooting when possible.

QuantaCade is an independent Joomla extension developer and is not official Joomla support. Some issues involving third-party extensions, hosting environments, server configurations, or other systems outside our development control may be beyond what we're able to resolve.

Open a Support Ticket