Joomla security for site owners: versions, extensions and access control
What the Joomla project fixes and what is set on your own Joomla site: supported versions and security announcements, extensions and their update sites, user groups and permissions, multi-factor authentication, the API application, configuration.php and backups.
It comes with an inventory and access control worksheet you fill in for your own site by reading its settings.
In this guide
Joomla inventory and access control worksheet
Paste the table into a spreadsheet, keep one copy per site, and fill in the inventory rows before the access control rows. The columns give the place to look, what the Joomla User Guide, the Joomla project or the Joomla 6.2.0 source says on that point, the facts to note down and the evidence worth keeping.
How to use itHide the instructions
Every step reads a screen, web page, setting, list, web server configuration file or file listing; none saves a form, changes a permission, resets a token, runs an update or opens a backup. For configuration.php, API tokens, the update token and download keys, write down that each exists and where, never the value. Documentation details are as those sources gave them on 14 November 2026, and each default is marked as either what a new 6.2.0 installation writes or the form default in the 6.2.0 source.
17 rows
Area
Where to look
Inventory: Joomla core version and support
- Where to look
- The version number in the top toolbar of the administrator area, next to the site name, and the roadmap on the Joomla Developer Network for your major series.
- What Joomla says
- The release cycle page says a release stops being supported when the next minor release comes out, and that after x.4.0 the project fixes bugs for one year and makes security fixes for two years. Read on 14 November 2026, the roadmap gave 12 October 2027 as the end of security-fix-only support for 5.x and 16 October 2029 for 6.x, and called its dates tentative.
- What to record
- The installed version, its major and minor series, whether a newer patch or minor release exists in that series, and the support end dates the roadmap gives, with the date you read them.
- Evidence to keep
- A dated screenshot of the toolbar version, and the roadmap URL with the date read.
Inventory: Joomla Update settings
- Where to look
- The update channel settings on the Joomla Update: Options page (the User Guide reaches Joomla Update through the Joomla link in the System Dashboard's Update panel), and the automated update status icon on the Home Dashboard. In the 6.2.0 source, the same options page has an "Automated Updates" group that shows the "Update Token" when automated updates are on: leave that group closed.
- What Joomla says
- In the 6.2.0 source, "Update Channel" offers "Default", "Joomla Next" and "Custom URL", "Automated Update" appears only with the "Default" channel and "Minimum Stability" set to "Stable", and enabling automated updates registers the site with a Joomla project service. The Quick Icon - Joomla! Automated Update Status Notification plugin, described as notifying you when you visit the Home Dashboard page, has statuses such as "Automated Updates are enabled." and "Automated Updates connection broken."
- What to record
- Update Channel, Minimum Stability, whether Confirm Backup Checkbox is set to show, and the automated update status text as the Home Dashboard shows it. Never the update token.
- Evidence to keep
- A dated screenshot of the update channel settings and of the status icon. Check which tab is open before you take a screenshot.
Inventory: security announcements and notifications
- Where to look
- The Security Announcements page on the Joomla Developer Network and its RSS feed; System / Scheduled Tasks, Update Notification item; the plugins list, for Quick Icon - Joomla! Update Notification and Task - Joomla! Update Notification.
- What Joomla says
- Each announcement gives the affected versions, a CVE number and the release to upgrade to. The update notification task emails Super Users when it finds a new version, is triggered by site activity, and sends to every Super User when its email field is blank.
- What to record
- Who reads the feed, whether the task and the quick icon plugin are enabled, who receives the emails, and each announcement whose affected installs include your version, with its fixed release.
- Evidence to keep
- Announcement URLs with the date read, and a dated screenshot of the task's settings.
Inventory: installed extensions
- Where to look
- The installed extensions list, including disabled entries ("Extensions" under "Manage" in the 6.2.0 source's System Dashboard menu), and the VEL's live, resolved and abandoned lists.
- What Joomla says
- For a vulnerable extension, the User Guide says removing its menu links, or unpublishing a module, is not enough while its files exist on the server. The VEL recommends uninstalling extensions in its live list, where no patch is known, and updating when your site uses a vulnerable version in its resolved list, and says it does not promise to test or validate reports.
- What to record
- One line per extension: name, type, location, version, author, enabled or not, where it came from (Joomla Extensions Directory, vendor or developer), and its VEL status with the date checked.
- Evidence to keep
- A dated screenshot or export of the list.
Inventory: available updates and download keys
- Where to look
- The list of available extension updates ("Extensions" under "Update" in the 6.2.0 source's System Dashboard menu), and each extension's page on its developer's site or the Joomla Extensions Directory. Leave the update sites list ("Update Sites" in the same menu) closed, because in the 6.2.0 source it prints each entered download key in full.
- What Joomla says
- In the 6.2.0 source, the installer says an extension that restricts updates, typically one with paid downloads, needs a "Download Key" from its developer, and that updates for the extension will not work until its key is entered. The extensions update list marks such an update with a "The Download Key is missing" button.
- What to record
- Each update the list shows as available, each one marked "The Download Key is missing", and for every extension in the inventory, whether its developer still publishes releases for your Joomla series, with the date checked. Never a key.
- Evidence to keep
- A dated screenshot of the extensions update list.
Inventory: templates and overrides
- Where to look
- The site and administrator template lists ("Site Templates" and "Administrator Templates" under "Templates" in the 6.2.0 source's System Dashboard menu), and each template's override files.
- What Joomla says
- For an update that changes the original of an override file, the 6.2.0 templates component has the message "The original of the template override files listed below has been updated." In a new 6.2.0 installation, "Valid Source Formats" include php, and saving a template source file needs the global "Super User" permission.
- What to record
- Each site and administrator template with its version and where it came from, how many override files it has, and any override listed as having an updated original.
- Evidence to keep
- A dated screenshot of each template's override list.
Access: Super Users and administrator accounts
- Where to look
- Users → Manage, filtered by group, and Users → Groups.
- What Joomla says
- The best practices page says anyone with a Super User role can perform any action in Joomla and only Super Users can add, edit and remove Super Users. A new 6.2.0 installation gives "Super User" to the Super Users group and "Administrator Login" to Manager, whose child group is Administrator.
- What to record
- Every account in Super Users, Administrator and Manager, and in any custom group allowed Administrator Login, each matched to a named person, with its enabled state and Last Visit date. Flag accounts nobody can name and accounts of people who have left.
- Evidence to keep
- A dated export or screenshot of the filtered list, with personal details trimmed.
Access: global permissions
- Where to look
- Home Dashboard → Global Configuration, Permissions tab, one group at a time.
- What Joomla says
- The User Guide calls these the starting point from which component and item permissions may inherit or override. The 6.2.0 actions include "Site Login", "Administrator Login", "Web Services Login", "Offline Access", "Super User" and "Access Administration Interface".
- What to record
- For each group, which of those actions shows as allowed, and any group other than Super Users holding "Super User" or "Web Services Login".
- Evidence to keep
- A dated screenshot for each group.
Access: reach of the administrator area
- Where to look
- The web server configuration or .htaccess file that applies to /administrator and /api, and the host's control panel.
- What Joomla says
- The best practices page says it is wise to limit access to the administrator backend by IP filtering, for example with an .htaccess file in the directory, and that security extensions can do the same.
- What to record
- Whether an address restriction or server password covers /administrator, whether anything covers /api, and who maintains it.
- Evidence to keep
- The relevant lines with the date read, with addresses trimmed if the worksheet will be shared.
Access: registration and default groups
- Where to look
- Users → Manage, then the Options button: "Allow User Registration", "New User Registration Group" and "New User Account Activation", which the User Guide places there, and "Guest User Group", which the 6.2.0 source's users options hold beside them.
- What Joomla says
- The User Guide says self-registration is disallowed by default, and that the New User Registration Group should be Registered unless there is good reason otherwise. A new 6.2.0 installation sets the first two to No and the Registered group.
- What to record
- Each value, and the reason when registration is on or the registration group sits above Registered.
- Evidence to keep
- A dated screenshot of the options.
Access: multi-factor authentication
- Where to look
- The "Multi-factor Authentication" settings in Users: Options, the plugins list filtered to the multi-factor authentication plugins, and the "MFA" column that the 6.2.0 source adds to the Users → Manage list.
- What Joomla says
- In the 6.2.0 source, "Enforce Multi-factor Authentication" requires members of the selected groups to set it up and is empty in a new 6.2.0 installation, and "Multi-factor Authentication after silent login" has the form default No. The User Guide says Fixed Code should not be enabled on a production site. The "MFA" column shows when a multi-factor authentication plugin is enabled and marks users with a method recorded.
- What to record
- The groups under Enforce and under Disable, the silent login setting, "Maximum MFA tries" and "MFA limit block time (in hours)", which methods are enabled, whether Fixed Code is disabled, and for each account in the administrator accounts row whether the MFA column shows a method.
- Evidence to keep
- Dated screenshots. No codes, secret keys or backup codes.
Access: text filters
- Where to look
- Home Dashboard → Global Configuration, Text Filters tab.
- What Joomla says
- The User Guide says the filters apply to all text editor fields submitted by users in the selected groups. In the 6.2.0 source, the types include "Default Forbidden List", "No HTML" and "No Filtering", and a parent group set to "No Filtering" can't be overridden in its child groups.
- What to record
- Each group's filter type, and every group set to "No Filtering" with the reason it needs it.
- Evidence to keep
- A dated screenshot.
Access: API application and tokens
- Where to look
- "Web Services Login" in the Global Configuration permissions; the plugins list for "API Authentication - Web Services Joomla Token", "API Authentication - Web Services Basic Auth", "User - Joomla API Token" and the webservices plugins; the "Joomla API Token" settings on each API user's profile, opened from a different Super User's account and closed without saving, since a token is shown only to its owner (have another Super User read your own); and "Enable CORS", which the 6.2.0 source places in Global Configuration's web services settings.
- What Joomla says
- In a new 6.2.0 installation, "Web Services Login" belongs to Super Users, the user token plugin's allowed groups default to Super Users, Basic Auth is disabled and "Enable CORS" is off. You cannot see another user's token, but you can enable, disable or reset it.
- What to record
- The groups with Web Services Login, each plugin's state and the token plugin's allowed groups, each account whose token is "Active" and what uses it, and the CORS setting with its allowed origin. Never a token.
- Evidence to keep
- Dated screenshots of the permissions and plugin settings, and a list of account names with their token state.
Access: configuration.php and folder permissions
- Where to look
- System Information ("System Information" under "Information" in the 6.2.0 source's System Dashboard menu), then its "Folder Permissions" list, leaving its "Configuration File" view closed; the host's file manager or an ls -l listing of the site root.
- What Joomla says
- In the 6.2.0 source, "Folder Permissions" lists configuration.php and the core folders as "Writable" or "Unwritable" to PHP, and saving Global Configuration tries to leave configuration.php at 0444 when the PHP process owns the file. The User Guide gives 644 for files and 755 for directories as usual server defaults, and says very open permissions such as 777 may be reset to 755 after installation.
- What to record
- The numeric mode of configuration.php and whether it shows as Writable, every folder shown as Writable, and any file or folder set to 777.
- Evidence to keep
- A dated screenshot of Folder Permissions, after checking which tab is open, and the listing line for configuration.php. Do not open the file.
Access: configuration copies, debug and error output
- Where to look
- Global Configuration's "Debug System" and "Path to Log Folder", which the User Guide places there, and "Error Reporting", "Force HTTPS" and "Path to Temp Folder", which the 6.2.0 source's Global Configuration form holds; a file listing of the web root for .htaccess, htaccess.txt and any copy of configuration.php under another name.
- What Joomla says
- In the 6.2.0 source, the description of "Debug System" says the technical information it displays can be a security risk if left enabled on live sites, and the description of "Error Reporting" says to use None on live sites for security reasons. The 6.2.0 installer writes "System Default". The log and temp folder descriptions say not to use a system-wide folder such as /tmp. The User Guide calls renaming htaccess.txt to .htaccess the normal practice.
- What to record
- Each value; on Apache or LiteSpeed, whether .htaccess exists and matches the rules in this version's htaccess.txt; and each copy of configuration.php by path, recording only that it exists.
- Evidence to keep
- Paths, values and dates only. Never the contents of configuration.php or of a copy.
Access: backup handling
- Where to look
- The backup extension's list of backups, the host's backup tool, and a file listing of the web root.
- What Joomla says
- The User Guide's backup page describes a site as its files and its database, says not to rely on host snapshots for Joomla site recovery, passes on the forum advice not to restore a backup on top of a faulty site, and for a command-line database restore says to upload the archive to a temporary location outside your web tree.
- What to record
- What each backup covers, where it is stored and whether that folder is inside the public web root, how often it runs, the date of the last one, whether one was taken before the last update, how many are kept, who can reach the storage, and the date of the last test restore, if any.
- Evidence to keep
- File names, sizes and dates only. Do not download or open an archive for the worksheet.
Access: User Actions Log
- Where to look
- Users → User Actions Log and its options, and the plugins list for Action Log - Joomla and System - User Actions Log.
- What Joomla says
- Only Super Users have access to the log. Its options choose which events are logged and whether IP addresses are included, and a new 6.2.0 installation leaves IP logging off. The System - User Actions Log plugin sets the number of days after which entries are deleted, and zero means they are never deleted automatically.
- What to record
- Whether both plugins are enabled, the events logged, the IP logging setting and the retention in days.
- Evidence to keep
- A dated screenshot of the options. Leave the log entries in place.
Where Joomla sits in your website
Joomla is a content management system.
A Joomla site has a public site, an administrator area that staff sign in to, and an API application. The Joomla User Guide notes that site login and administrator login are treated separately, although a Global Configuration setting allows them to be combined.
In the 6.2.0 source, Joomla's API token plugin describes the API application as remote access to your site, and the web services examples in Joomla's programmers documentation send their requests to https://example.org/api/index.php/v1.
Around the core sit extensions, such as components, modules and plugins, and templates. The User Guide says third-party extensions may be found on professional developers' websites, personal blogs, GitHub and similar repositories and the Joomla Extensions Directory.
Below Joomla sit the web server, PHP and the database. The User Guide's backup page describes a Joomla site as the files in the Joomla root directory tree and a database located somewhere else on the host server, which holds most of the site content.
Its Global Configuration page says that on installation, a Joomla site creates configuration.php in the root of the site, holding configuration values that apply to the whole site, among them the database credentials entered during installation.
This guide was written from the Joomla User Guide, the Joomla project's security pages and roadmap, the programmers documentation for version 6.2, the Vulnerable Extensions List and the Joomla CMS source code at the 6.2.0 release tag, all read on 14 November 2026. Where a default comes from the source code, the page says whether it is what a new 6.2.0 installation writes or the form default in the 6.2.0 source.
A site installed earlier, or changed since, can differ, which is why the worksheet records what your site actually has.
Is Joomla secure? What the project fixes and what is set on your site
There is no yes or no answer on this page.
Instead it shows who handles which part. The Joomla! Security Strike Team (JSST) oversees the project's security issues. Its page says the team operates with a limited scope: it only directly responds to issues with the core Joomla! CMS and Framework, and processes reports about the joomla.org network of websites.
It does not directly handle potential vulnerabilities in extensions and asks that those be reported to the extension's vendor, although the Joomla project assigns CVE IDs for extension vulnerabilities as the responsible CNA.
The same page sets the release rules. Verified vulnerabilities are announced publicly only after a release that fixes them is issued, and announcements do not contain step-by-step instructions. Critical and high-level vulnerabilities trigger an immediate release cycle, and the project may publish an advisory giving the scheduled release window so that site owners can prepare.
Moderate vulnerabilities may trigger a release cycle depending on the issue, while low and very low ones, and moderates that do not trigger one, go into the next scheduled maintenance release.
The JSST's impact table puts XSS attacks and write ACL violations, meaning editing or creating content where that is not allowed, at moderate, and read ACL violations, meaning reading content where that is not allowed, at low. The page adds that these descriptions are generic guidelines and that each vulnerability will be assessed for damage potential and ranked accordingly.
It also says the JSST will actively monitor every version of the CMS and Framework that is being developed and supported.
What the same documentation describes as tasks and settings on the site itself:
- Installing releases. The User Guide's update page says that although Joomla will notify you when an update is available, it requires you to carry out the update. The roadmap lists Automated Core Updates under the main features of Joomla 5.4, and the Joomla Update options in the 6.2.0 source include an "Automated Update" setting, covered below.
- Extensions. The JSST asks that extension vulnerabilities go to each extension's vendor. The Vulnerable Extensions List collects reports, and its about page says the team does not promise to test or validate them.
- Who can do what. The User Guide describes user groups and access levels set in the users options, and action permissions set in Global Configuration, in components and on items.
- Multi-factor authentication. Joomla ships it, and the users options decide which groups must use it. In a new 6.2.0 installation, the list of groups it is enforced for is empty.
- The server and the backups. The User Guide's backup page says hosting snapshots may cover everything in the account, and not to rely on them for Joomla site recovery.
What a security release changes
This page's reading: a Joomla security release is a change to Joomla's own code. It is not what updates a third-party extension, removes an extra Super User account, enforces multi-factor authentication or moves a backup out of the web root, and those are the things the worksheet records.
Joomla security updates: supported versions and the release cycle
Joomla's programmers documentation describes the release cycle the project has used since version 4.0: a major version every two years, planned for October in odd-numbered years, a minor release every six months within those two years, and patch releases usually every six weeks.
The last minor release of a series is a bridge release with no new features, and an update to the next major release can only be made from it, usually a x.y.4 release.
The same page sets the support rules. A release stops being supported when the next minor release comes out: for example, the x.2.z line goes out of support when x.3.0 is published. After the x.4.0 release date, the project fixes bugs for one year and makes security fixes for two years.
The supported upgrade path runs first to the fully patched minor release of the series you are on, then to the fully patched minor release of the next major series, and updates from end-of-life releases are not, by definition, supported.
Read on 14 November 2026, the project roadmap described Joomla 5.x and 6.x as supported major release series. For 5.x it gave 13 October 2026 as the end of regular bugfix support and 12 October 2027 as the end of security-fix-only support.
For 6.x it gave 17 October 2028 and 16 October 2029. The roadmap says its dates are tentative, so read it again for your own series when you fill in the worksheet.
The update channel, automated updates and notifications
The User Guide places the update channel on the Joomla Update: Options page, and says that with the channel set to "Default", updates within the current major version are notified. In the 6.2.0 source, those options group it under "Update Source", described as configuring where Joomla gets its update information from: "Update Channel" offers "Default", "Joomla Next" and "Custom URL", and "Minimum Stability" runs from development releases up to "Stable".
In the 6.2.0 source, the "Automated Update" setting appears only when the channel is "Default" and the minimum stability is "Stable". The description of the "Automated Updates" settings says automated updates are only available for sites that are publicly accessible on the internet, and that enabling them registers the site with a service provided by the Joomla project.
It says the registration allows the Joomla project to access information about the site and server: the site URL, PHP version, database type and version, CMS version and server operating system type and version.
Once it is on, the options show an "Update Token", described as the token the site uses to authenticate with the Joomla Automated Updates server, and a "Last Checked" date.
The description of "Last Checked" says that if the date is too old, something is wrong with the automated updates and the process should be re-initiated by re-saving the configuration.
Plugins tell people about updates. The User Guide describes Quick Icon - Joomla! Update Notification, which checks for Joomla updates and notifies you when you visit the Home Dashboard page, and Task - Joomla! Update Notification, which periodically checks for new versions and, when one is found, triggers an email to Super Users.
The task is triggered by site activity, and when its Super User email field is left blank, every Super User receives the email.
In the 6.2.0 source, Joomla Update can ask for a tick against "I'm aware that a backup before any update is highly recommended." in the final step before an update is applied, controlled by the "Confirm Backup Checkbox" option. The User Guide says the update process creates or appends to administrator/logs/joomla_update.php, a log of each update's major steps.
Joomla vulnerabilities: Security Announcements and the Vulnerable Extensions List
Core advisories are published as Security Announcements on the Joomla Developer Network.
The page describes the feed as announcements of resolved security issues in Joomla! software releases and says it can be followed in an RSS reader. Each announcement gives the affected versions, a CVE number, a description, the affected installs and a solution naming the release to upgrade to.
These announcements, read on 14 November 2026, bear on rows of the worksheet. Each is given in the announcement's own terms, and the Security Announcements page is where later entries appear.
- CVE-2023-23752, improper access check in webservice endpoints: an improper access check allows unauthorised access to webservice endpoints. Affected installs: Joomla 4.0.0 to 4.2.7. Solution: upgrade to Joomla 4.2.8.
- CVE-2026-71574, inconsistent ACL checks for mutating webservice endpoints: an improper access check allows unauthorised users to perform mutation actions in webservice endpoints where the same mutation was restricted in the backend UI. Affected installs: Joomla 4.0.0 to 5.4.7 and 6.0.0 to 6.1.2. Solution: upgrade to Joomla 5.4.8 or 6.1.3.
- CVE-2026-71573, improper CORS origin validation: an improper implementation prevented configured CORS origins from being properly validated in CORS requests. Affected installs: Joomla 4.0.0 to 5.4.7 and 6.0.0 to 6.1.2. Solution: upgrade to Joomla 5.4.8 or 6.1.3.
- CVE-2026-73337, MFA authentication bypass: insufficient state checks lead to a vector that allows two-factor checks to be bypassed. Affected installs: Joomla 4.0.0 to 5.4.7 and 6.0.0 to 6.1.2. Solution: upgrade to Joomla 5.4.8 or 6.1.3.
- CVE-2026-92227, MFA authentication bypass through remember-me cookies: the premature issuance of a remember-me cookie leads to an MFA bypass vulnerability. Affected installs: Joomla 4.0.0 to 5.4.8 and 6.0.0 to 6.1.3. Solution: upgrade to Joomla 5.4.9 or 6.1.4.
- CVE-2026-73373, unrestricted uploads of SHTML files: the default list of dangerous files did not include SHTML files, and on servers that executed these files, that could lead to code execution. Affected installs: Joomla 1.0.0 to 5.4.7 and 6.0.0 to 6.1.2. Solution: upgrade to Joomla 5.4.8 or 6.1.3.
The Vulnerable Extensions List
Extensions are tracked elsewhere. The Vulnerable Extensions List (VEL) keeps a live list of vulnerable extensions for which no patch is known to exist and recommends uninstalling any listed there. Patched extensions move to its resolved list, which names vulnerable versions for which a patch exists and recommends updating if your site uses one of them.
Its abandoned list covers products ignored by their owner and manufacturer with no support available, which it says may or may not be vulnerable.
The VEL's about page says the list is compiled from found information, may not be an up to date accurate list, and that the team does not promise to test or validate the reports.
This page's reading: a VEL entry is a reason to act on an extension, and the absence of one is not evidence that an extension has no flaws. The dependency security guide in this library covers deciding what to update first when several components are behind.
Extensions and templates: versions, update sites and download keys
The User Guide reaches Joomla Update through the System Dashboard's Update panel, and lists Manage, Information, Update and Templates among that dashboard's panels.
In the 6.2.0 source, the menu definition behind the System Dashboard puts links labelled "Extensions" and "Update Sites" under "Update", beside the Joomla link, and "Extensions" and "Plugins" under "Manage". The installed extensions list and the list of available updates are where the inventory takes each extension's version and update status from.
Paid extensions add a step. In the 6.2.0 source, the installer's description of a "Download Key" says an extension that restricts updates, typically one with paid downloads, needs a key obtained from its developer and entered to unlock its updates. Where a key is missing, the update sites list carries the tip that updates for that extension will not work until its key is entered.
This page's reading: until its key is entered, an extension marked "The Download Key is missing" does not receive its updates through Joomla, security fixes included.
A caution for the worksheet. In the 6.2.0 source, the update sites list prints an entered download key in full beside its update site, while the template for the extensions update list marks a missing key with a "The Download Key is missing" button and prints no key. The worksheet reads the extensions update list for that reason.
The User Guide's page on vulnerable extensions makes a point the inventory has to reflect. Writing about a vulnerable extension, it says simply removing the menu links to an extension, or unpublishing a module, is not enough to protect your site: as long as the extension's files exist on your server, an attacker can bypass the Joomla index file and target any file of any extension directly.
It also says not to trust an extension to remove all of its files when uninstalled, and to compare what is on the server with the file list in the extension's XML file. This page's reading: disabled and unpublished extensions stay on the inventory until their files are gone.
Templates and their overrides
Templates carry code too. For the case where an update changes the original of a file a template overrides, the 6.2.0 source's templates component has the message "The original of the template override files listed below has been updated. This list aids you in reviewing those changes and marking them as checked as you progress." This page's reading: an override written before a security fix keeps its own copy of the layout until someone reviews it, so the list is worth reading after every update.
In a new 6.2.0 installation, the templates component's "Valid Source Formats" include php, and the controller that saves a template source file checks the global core.admin permission, which Global Configuration labels "Super User". This page's reading: on those settings, only accounts holding "Super User" can save template code from the administrator area, which is one more reason to keep that list of accounts short.
Joomla ACL: user groups, access levels and permissions
The User Guide describes access control as a who part and a manipulate part.
Who is set up with user groups and access levels in the users options. What they can do is set with action permissions in Global Configuration, in each component's settings and on individual items, and settings at each level can be overridden at the level below.
It says the default user groups are set up with parent and child relationships. A new 6.2.0 installation creates Public, Registered, Author, Editor, Publisher, Manager, Administrator, Super Users and Guest, with Administrator a child of Manager.
The User Guide calls the Global Configuration permissions the starting point from which permission settings in components or individual items may inherit or override. In the 6.2.0 source their actions include "Site Login", "Administrator Login", "Web Services Login", "Offline Access", "Super User" and "Access Administration Interface". The 6.2.0 database script for a new installation allows "Administrator Login" for the Manager group and gives "Super User" and "Web Services Login" to the Super Users group alone.
The User Guide confirms that Manager and Administrator are allowed Administrator Login and that Author, Editor and Publisher are not.
The User Guide's best practices page says anyone with a Super User role is able to perform any action within the Joomla system, that only Super Users can add, edit and remove Super Users, and that a team member whose work needs fewer permissions should get the minimum access.
Its registration page says self-registration is disallowed by default, and that the New User Registration Group should be Registered unless there is good reason for it to be something else. A new 6.2.0 installation sets "Allow User Registration" to No and "New User Registration Group" to the Registered group.
Text filters belong with access control too. The User Guide says the settings on Global Configuration's Text Filters tab apply to all text editor fields submitted by users in the selected groups. In the 6.2.0 source, the filter types include "Default Forbidden List", "No HTML" and "No Filtering", and the settings warn that a parent group set to "No Filtering" can't be overridden in its child groups.
The 6.2.0 help text for the filters says the tags on the Default Forbidden List include script, iframe and object.
This page's reading: a group set to "No Filtering" has none of those tags removed from what it saves, so the worksheet records which groups have it.
The authentication failures guide in this library covers sign-up, login and password reset flaws in general. The rest of this page stays with Joomla's own settings.
Two-factor and multi-factor authentication in Joomla
The User Guide describes Joomla's multi-factor authentication as adding optional two step verification methods to Joomla login: after the username and password, the user is asked for the second step and is redirected to a captive login page until a correct one is given.
It says the methods shipped with core include Verification Code, YubiKey, Web Authentication and Authentication Code by Email, plus Fixed Code, which is intended for testing and illustration, is disabled by default and should not be enabled on a production site.
Who must use it is a setting. The User Guide says the Users: Options form lets you require or disable multi-factor authentication by user group. In the 6.2.0 source, its "Multi-factor Authentication" settings include "Enforce Multi-factor Authentication", which requires any member of the selected groups to enable multi-factor authentication before using the site, and "Disable Multi-factor Authentication", which exempts members of the selected groups, even if they have set up methods.
In a new 6.2.0 installation both lists are empty. On those settings, no group is required to set it up until someone chooses one.
Silent logins need a decision of their own. In the 6.2.0 source, "Multi-factor Authentication after silent login" asks whether a user should have to go through multi-factor authentication after a login that needs no username and password, such as the Remember Me feature or passkeys. Its form default in the 6.2.0 source is No, and a new 6.2.0 installation stores no value for it.
The silent response types default to cookie, the Remember Me feature, and passwordless, meaning passkeys. The same settings include "Maximum MFA tries" and "MFA limit block time (in hours)", with form defaults of 10 and 1.
The announcements for CVE-2026-73337 and CVE-2026-92227 both concern multi-factor authentication. The solution the announcements give for CVE-2026-73337 is an upgrade to Joomla 5.4.8 or 6.1.3, and for CVE-2026-92227, which involves remember-me cookies, an upgrade to Joomla 5.4.9 or 6.1.4. The worksheet's multi-factor row is read alongside the core version row for that reason.
Checking who has set it up takes a different route. The User Guide says the Multi-factor Authentication tab on a user's profile is only visible to the account owner, and that even Super Users do not see it for other users.
In the 6.2.0 source, the users list shows an "MFA" column whenever a multi-factor authentication plugin is enabled, with a check icon for each user who has a method recorded. That column is what the worksheet reads.
The Joomla API application and its tokens
The API application answers under /api.
The htaccess.txt file in the 6.2.0 source rewrites requests whose path starts with /api/ to api/index.php when no file or folder matches the path, and the programmers documentation sends its example requests with an X-Joomla-Token header. In the 6.2.0 source, the token authentication plugin first looks for an Authorization header carrying a Bearer token, then for the X-Joomla-Token header.
Settings that bear on who can use it include "Web Services Login" in the Global Configuration permissions, which a new 6.2.0 installation gives to the Super Users group alone, and the allowed user groups of the "User - Joomla API Token" plugin, which default in the 6.2.0 code to group 8, Super Users.
That plugin adds "Joomla API Token" settings, including "Active" and "Reset", which its text places on the user profile. The plugin's text says you cannot see the token for users other than yourself, but you can still enable, disable or reset their token, and that saving the profile of a user who has no token yet generates one.
In a new 6.2.0 installation, the database script enables "API Authentication - Web Services Joomla Token", the user token plugin and a webservices plugin for each of a list of core components, among them content, users, config and installer, and leaves "API Authentication - Web Services Basic Auth" disabled. The installer writes "Enable CORS" as off, with the allowed origin set to *.
In the 6.2.0 source, the token a user sees is an HMAC of a stored seed, keyed with the site secret from the global configuration, and the authentication plugin checks incoming tokens the same way. The plugin also refuses blocked users, users with a pending activation and users who must reset their password.
This page's reading: the secret in configuration.php is part of what makes every API token valid, which ties the API row of the worksheet to the configuration file row.
The announcements for CVE-2023-23752 and CVE-2026-71574 concern webservice endpoints. The announcement for CVE-2026-71573 concerns the validation of configured CORS origins, which the 6.2.0 source places in Global Configuration's web services settings. The worksheet records which of its plugins are enabled, which accounts hold an active token, and what, if anything, the business uses the API for.
configuration.php, file permissions and server settings
The User Guide's backup page says configuration.php contains the database name and access credentials, and in a new 6.2.0 installation the installer also writes a random site secret into it.
When Global Configuration is saved and the PHP process owns the file, the 6.2.0 source tries to set configuration.php to 0644 to write it, then tries to set it to 0444 and shows "Could not make configuration.php unwritable." if that fails. The User Guide says that on most Linux based hosting systems the file is set to 444.
For other files, the User Guide's page on UNIX permissions says the defaults servers normally assign are 644 for files and 755 for directories. Where the web installer reports directories as not writable, it says they might need 757, or in the worse case 777, and that these very open permissions may be reset back to 755 after the installer runs.
Where the host runs the web server as your own user, through phpsuExec or suExec, it says directories may only need 755 or 775.
Joomla can report its own view. In the 6.2.0 source, System Information's "Folder Permissions" list covers the core folders, the images and files folders, the log, temp and cache folders and configuration.php itself, and marks each "Writable" or "Unwritable" according to whether PHP can write to it.
The System Information model's method that returns the site configuration replaces the database host, user name and password, the FTP and SMTP user names and passwords, the Redis passwords, the proxy user name and password and the site secret with xxxxxx.
Its list leaves out the SMTP OAuth2 client secret and refresh token, which the 6.2.0 Global Configuration model treats as protected configuration fields, so the worksheet keeps the reader off System Information's "Configuration File" view.
Exposure also comes from copies. A copy of configuration.php kept under another name before an edit, or a backup archive that includes the site's files, carries the same credentials and secret. The worksheet asks for a file listing of the web root and records only whether such a copy exists and where it is, never its contents.
htaccess.txt, debug output and error reporting
Joomla ships htaccess.txt in the root directory. The User Guide says Apache's active file defaults to .htaccess, calls renaming htaccess.txt to .htaccess the normal practice alongside the SEO settings, and suggests merging it with any settings your host has already put in .htaccess. In 6.2.0 the file turns off directory listings, sets an X-Content-Type-Options: nosniff header where Apache's headers module is loaded, and, where the rewrite module is loaded, includes rewrite rules that attempt to block common exploit attempts in query strings.
The User Guide says not to edit htaccess.txt itself, since a Joomla update could overwrite it.
It adds that the file may change from one Joomla version to the next, and that if in doubt, or if strange problems occur after an update, you should make sure your .htaccess file is up to date.
The User Guide places "Debug System" in Global Configuration's Debug panel. In the 6.2.0 source, its description says the technical information displayed in that mode can be a security risk if left enabled on live sites, and the description of Global Configuration's "Error Reporting" says to use None on live sites for security reasons.
The 6.2.0 installer writes "Error Reporting" as "System Default", so on a new 6.2.0 installation the setting is not None until someone changes it.
In the 6.2.0 source, the descriptions of "Path to Log Folder" and "Path to Temp Folder" say not to use a system-wide folder such as /tmp, and the installer sets the log folder to administrator/logs and the temp folder to tmp in the site root.
"Force HTTPS" offers "None", "Administrator Only" and "Entire Site", and the installer writes None. The security misconfiguration guide in this library covers drift between intended and running settings in general.
Joomla backups: what they hold and where they are kept
The User Guide's backup page describes a Joomla site as its files and its database.
This page's reading: a backup has to cover both. The same page says hosting services often take snapshots of customer sites, that a snapshot might cover everything in the account, and not to rely on that for Joomla site recovery. The User Guide's update page opens with "Remember: Always back up your site before updating."
This page's reading: a backup that covers the files and the database is also a copy of configuration.php and of the site's data, and an archive stored inside the public web root is only as private as its file name and the server's rules, so the worksheet records where each backup lives and whether that folder sits inside the site's public root.
For restores, the User Guide passes on advice from the Joomla forums: do not restore a backup on top of a faulty site. For a database restore from the command line, it says to upload the archive to a temporary location outside your web tree. The worksheet records when a restore was last tested; it does not run one.
The User Actions Log as a record of change
The User Guide says the User Actions Log component provides an infrastructure to create an audit log of website activities, and that only Super Users have access to it, from Users → User Actions Log.
Its options choose which events to log and whether to include IP addresses, and a new 6.2.0 installation leaves IP logging off. The Action Log - Joomla plugin records core actions such as login and logout, and the System - User Actions Log plugin sets the number of days after which entries are deleted, with zero meaning they are never deleted automatically.
This page's reading: the log is the record a later review, or an incident responder, will ask for, so the worksheet notes whether it is on, what it captures and how long it keeps entries.
Joomla security best practices drawn from its documentation
This list is this page's own summary of the Joomla pages above.
Each item is a decision for whoever runs the site, and a worksheet row records whether it is in place.
- Run a supported series, move to each new minor and patch release in it as it comes out, and check the roadmap dates for that series.
- Follow the Security Announcements feed, and make sure the update notification emails reach a Super User who acts on them.
- Back up the site before each update, as the User Guide asks, and keep the backup confirmation checkbox set to show.
- Check each extension against the Vulnerable Extensions List, and uninstall extensions you no longer use rather than unpublishing them.
- Enter the download keys of paid extensions so that their updates arrive.
- Read the template override list after every update.
- Keep the Super Users group to named people who need it, and give everyone else the lowest group that does the job.
- Enforce multi-factor authentication for the groups that can sign in to the administrator area, and decide on purpose whether silent logins skip it.
- Leave "Web Services Login" and API tokens with the accounts that use the API, and know who owns each active token.
- Keep "Error Reporting" at None and "Debug System" off on the live site.
- On Apache or LiteSpeed, put the shipped htaccess.txt rules in place as .htaccess, merged with your host's settings, and compare them after each update.
- Keep backups out of the public web root, and test that they restore.
How to fill in the inventory and access control worksheet
Make one copy per site.
Fill in the inventory rows first: the core version they record decides which announcements apply to the access control rows that follow.
- Every row reads a screen, a web page, a setting, a list, a web server configuration file or a file listing. None saves a form, changes a permission, switches a plugin on or off, resets a token, runs an update, or downloads or opens a backup.
- Some rows need a Super User account, such as the User Actions Log, which only Super Users can open.
- Record names, never values. For configuration.php, API tokens, the update token and download keys, write down that each exists and where, and nothing more. Do not open configuration.php or a copy of it, and read settings from the Global Configuration form instead, leaving any masked password field masked.
- Stay off screens that display a secret. In the 6.2.0 source, the "Automated Updates" settings in Joomla Update's options show the update token when automated updates are on, an API user's "Joomla API Token" settings show the token to that user, the update sites list prints each entered download key, and the System Information model's configuration method leaves the SMTP OAuth2 client secret and refresh token unmasked, so System Information's "Configuration File" view stays closed. The rows say where to read the same facts instead.
- Put a date on each screenshot and export, and remove personal details before anyone outside the team sees the worksheet.
- Where a row shows something to change, note it and plan the change separately. The worksheet itself changes nothing.
- Fill it in again after a Joomla or extension update, a new extension or template, a new Super User or administrator, or a move to another host.
What the worksheet cannot show
The worksheet records configuration and lists.
It shows which Joomla version runs and whether its series is supported, which extensions and templates are installed, where they came from and whether updates are waiting, who holds which group and permission, whether multi-factor authentication is enforced, which API access is switched on, how configuration.php and the folders are set, and where backups are kept.
Anything outside those screens and files is outside the worksheet too, such as a flaw in an extension that no announcement names yet, a custom extension written for the site, a permission granted on a single category or article, or what the site does with a request its screens never send.
It is also a snapshot. Versions, accounts and settings change after the review, and the Security Announcements feed and the VEL gain entries. Write the date beside every row, and count any row filled in before the most recent Joomla or extension update as not yet checked.
If you think the site is already compromised, the worksheet is the wrong first step. The hacked website guide in this library covers the first hour. Incident response, forensics, malware cleanup and round-the-clock monitoring are not Clever Ops services, so start with your host and an incident response or cleanup specialist.
Where a Clever Ops assessment fits
This guide is for information only.
It names no Clever Ops service specific to Joomla, and nothing here is a test of Joomla. The people who run a Joomla site fill in the worksheet themselves, from their own settings.
The work Clever Ops does covers what a business's customers reach through a browser or an API. Where a business also runs a custom web application or API of its own, such as a customer portal beside its Joomla site, active testing of that application sits within a scoped web application penetration test.
That test runs signed in, from test accounts in each role in scope, against both the application and the API behind it. Before any of it starts, the owner of each target signs an authorisation, and the hosting provider's testing policy for that target is checked.
If the custom application was built or is hosted by Clever Ops, the report calls the work a security review, not an independent penetration test, and names who built the application and who hosts it. The report is evidence for a decision that someone else makes, such as a customer or an auditor, and it does not certify anything.
Frequently asked questions
No yes or no here: the answer sets out who handles what. The Joomla Security Strike Team only directly responds to issues in the core CMS and Framework, announces verified vulnerabilities only after a release that fixes them, and says it will actively monitor every version of the CMS and Framework that is being developed and supported. It does not directly handle extension vulnerabilities, and asks that those be reported to each vendor. Which groups must use multi-factor authentication, which accounts hold Super User and where backups are kept are settings and choices made on the site itself, and the worksheet records them.
Check the roadmap on the Joomla Developer Network for your major series. Read on 14 November 2026, it gave 12 October 2027 as the end of security-fix-only support for Joomla 5.x and 16 October 2029 for 6.x, and it says its dates are tentative. The release cycle in Joomla's programmers documentation adds that a release stops being supported when the next minor release comes out, and that updates from end-of-life releases are not, by definition, supported.
Core issues appear as Security Announcements on the Joomla Developer Network, which can be followed by RSS, and each one gives the affected versions, a CVE number and the release to upgrade to. Inside the site, the Task - Joomla! Update Notification plugin emails Super Users when it finds a new version, triggered by site activity. The JSST asks that extension issues be reported to each vendor, and the Vulnerable Extensions List keeps live, resolved and abandoned lists.
Yes. The User Guide says the multi-factor authentication methods shipped with Joomla core include Verification Code, YubiKey, Web Authentication and Authentication Code by Email. Whether anyone must use it depends on "Enforce Multi-factor Authentication" in the 6.2.0 users options, which is empty in a new 6.2.0 installation. "Multi-factor Authentication after silent login" has the form default No in the 6.2.0 source, and its description says silent logins are those that need no username and password, such as the Remember Me feature or passkeys. In the 6.2.0 source, the users list shows an "MFA" column when a multi-factor authentication plugin is enabled, with a check icon for each user who has a method recorded.
In a new 6.2.0 installation, "Web Services Login" belongs to the Super Users group alone, the API token plugin's allowed groups default to Super Users, the token authentication plugin is enabled and the Basic Auth plugin is disabled. Each token is personal: the plugin's text says you cannot see the token for users other than yourself, but you can still enable, disable or reset theirs. Past announcements, including CVE-2023-23752, concerned access checks on these endpoints.
For a vulnerable extension, the Joomla User Guide says removing its menu links or unpublishing a module is not enough, because while its files remain on the server an attacker can bypass the Joomla index file and target them directly. It also says not to trust an extension to remove all of its files when uninstalled, and to compare what is on the server with the file list in its XML file. For extensions in the Vulnerable Extensions List's live list, where no patch is known, the list recommends uninstalling.
Scope the right test for your application
Tell us what you have built, who uses it and when it needs to launch. You will get a plain-English recommendation: a website audit, a web application test or a referral to a specialist.