How to Check Extensions After a Joomla Security Incident
After a Joomla security incident, every installed extension should be treated as part of the investigation. Confirm what is installed, remove software you no longer need, compare retained extensions with trusted vendor releases, and verify that the vulnerability that allowed the incident has actually been closed.
Inventory every installed extension
In the Joomla Administrator, review components, modules, plugins, templates, packages, libraries, and other installed extensions. Record the extension name, version, provider, enabled state, and whether the extension is still required. Also inspect the filesystem for old extension directories or abandoned site copies that may no longer appear clearly in the Administrator.
Check each extension against trusted sources
For every retained third-party extension, confirm the installed version against the developer's current supported release and security information. Check Joomla's Vulnerable Extensions List and the vendor's advisories where applicable. An extension can be fully updated yet still unsafe if the product is abandoned or the installed branch is no longer supported.
Replace questionable extension files
If an extension may have been modified, reinstall it from a clean package obtained from the original trusted developer. Do not assume that installing an update over compromised files removes malicious files that are not part of the package. When trust in the filesystem is lost, compare against a clean package or rebuild the extension files in a clean site copy.
Remove unused and vulnerable extensions
Uninstall extensions that are no longer needed and remove leftover executable files when the vendor's uninstall process does not clean them up. If an extension has a known unpatched vulnerability, disable public access to the affected functionality and replace or remove the extension rather than relying on obscurity.
Review plugins, update sites, and privileged integrations
Pay special attention to system, authentication, user, installer, and API-related plugins because they can affect every request or privileged workflow. Review extension update sites for unexpected URLs and rotate license keys, API tokens, webhook secrets, or other credentials that could have been exposed during the compromise.
Verify before reopening the site
Update or reinstall retained extensions, clear caches, and test the frontend and Administrator in a controlled environment. Review logs for recurring exploit attempts and confirm that suspicious files, users, scheduled jobs, or configuration changes do not return. Extension review is only one part of recovery; also rotate credentials, inspect the database, replace compromised core files, and address the original entry point.
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.