Joomla 6.2 (Mwezi) shipped on 13 October 2026. Most of the headlines are about editing: TinyMCE now opens the Joomla Media Manager, there’s a unified link picker, and there’s a Read More button. If you look after client sites, though, the change I’d pay most attention to is smaller and lives on the update screen.
What changed
Extension developers can now flag a release as a security update, with a severity from None to Critical. Joomla highlights flagged updates in System → Update → Extensions and on the dashboard quick icon.
Before this, a security fix looked exactly like a routine version bump unless you went and read the changelog. Now the important one stands out.
There are two caveats worth keeping in mind:
- It only helps when the developer sets the flag. An unflagged update can still contain a security fix, so don’t read “no flag” as “no risk”.
- It shows up per site, inside each site’s own admin.
How to use it on one site
- Get the site onto Joomla 6.2. From 5.4 it’s an upgrade, not a migration, and most extensions work with the “Behaviour – Backward Compatibility 6” plugin enabled while you check them.
- After each update check, look at the dashboard quick icon. A highlighted security update goes to the top of your list.
- Take a database and file backup before you apply it, and keep it somewhere other than the server itself.
- Apply the flagged update first, then load the front end and any pages that use that extension.
- Write down what you changed and when. If something breaks next week, that record saves you an hour.
The problem with twenty sites
That loop is fine for one site. Across twenty or fifty, step two means logging into every admin just to look at a quick icon, and step five usually lives in someone’s head.
The same day, Joomla 5.4.10 was released as the last 5.x bugfix release. 5.4 now gets security fixes only, for one more year. So most fleets will run a mix of 5.4 and 6.2 sites for a while, plus WordPress sites that don’t have this flag at all. If you’re still planning that move, our Joomla 5.4 fleet checklist covers it.
A fleet routine that holds up
This is the loop I’d run weekly, and straight away when a serious advisory drops:
- See every pending update in one place. Joomla and WordPress side by side, so nothing waits on someone remembering to log in.
- Back up first, off the server. Database and files, uploaded somewhere you can reach even if the site is down.
- Run security-relevant updates first, in batches. Use the Joomla flag on the site, the vendor advisory, or a CVE notice to decide what goes first.
- Watch uptime after the run. A broken extension usually shows up as an error or a slow response within minutes.
- Keep the record. What ran, what failed, what got retried, and what the client should hear about.
Where CMS Inspect fits
I built CMS Inspect for exactly that loop. It’s an operations layer for WordPress and Joomla fleets:
- Both platforms in one dashboard, with shared monitoring, updates, backups, security and reporting.
- Updates you can queue, run and retry, with clearer state transitions and command visibility, so you can see what changed and what failed.
- Database and file backups uploaded to Google Drive or Dropbox, so recovery files live outside each website.
- Uptime monitoring with status history and response context, so a bad update shows up quickly.
- Security findings you can triage, with verified false positives suppressed so the queue stays useful.
- Client-ready reports that show what changed and what was resolved.
Joomla’s new flag tells you which update matters on a site. CMS Inspect helps you do the work across all of them and keep the proof.
The core dashboard is free, and advanced operations are $1 per active site per month. If you look after more than a handful of Joomla or WordPress sites, it’s worth ten minutes: cmsinspect.com.
Sources: Joomla 6.2 announcement https://www.joomla.org/announcements/release-news/joomla-6-2-is-here.html and Joomla 5.4.10 release https://www.joomla.org/announcements/release-news/joomla-5-4-10-bugfix-release.html


[…] Read the developer’s changelog for security notes. Some releases are clearly marked as security updates, many aren’t. AcyMailing 11.1.2 is the first AcyMailing release tagged as a security update in Joomla’s update data, so recent Joomla versions badge it. That flag only helps if the update shows up in the first place. (More on that flag in Joomla 6.2 security update flags: how to act on them across many sites.) […]