Joomla versions
Joomla: update to 6.2.0 or 5.4.10. 4 and older no longer get fixes.
Data: .
Which Joomla branch to run
The newest safe release is the newest release of a branch that still gets fixes and that no CVE record we read names as affected. Records whose versions we cannot place on a branch are named at the end of the page.
| Branch | Status | Newest safe release | Upgrade to |
|---|---|---|---|
| 664 CVE records that this page reads | Bug and security fixes until 17 October 2028, then Security Support until 16 October 2029 | 6.2.0 | 6.2.0 (this branch) |
| 586 CVE records that this page reads | Security fixes only until 12 October 2027 | 5.4.10 | 5.4.10 (this branch) |
| 437 CVE records that this page reads | Ended on 14 October 2025 | None, the branch has ended | 5.4.10 (move to 5) |
| 344 CVE records that this page reads | Ended on 17 August 2023 | None, the branch has ended | 5.4.10 (move to 5) |
Exploited, or likely to be
CVE records for Joomla that CISA lists as exploited, that have a public exploit, or that EPSS rates 0.50 or more, with the releases that fix each where the record names them. None of the 3 records shown names one.
| Record | Signs of exploitation | Fixed in |
|---|---|---|
| CVE-2023-23752[20230201] - Core - Improper access check in webservice endpoints5.3 Medium · published 16 February 2023 | On CISA's list Metasploit module Exploit-DB entry EPSS 0.50 or more | The record names no fixed release for 4. |
| CVE-2021-26030[20210401] - Core - Escape xss in logo parameter error pagespublished 14 April 2021 | EPSS 0.50 or more | The record names no fixed release for 3. |
| CVE-2021-23124[20210102] - Core - XSS in mod_breadcrumbs aria-label attributepublished 12 January 2021 | EPSS 0.50 or more | The record names no fixed release for 3. |
What this page counts
The branches, their dates and the newest release of each are from the product lifecycle data credited under Sources. A later release that a CVE record names as a fix counts as the newest too.
132 CVE records that the Joomla project's CVE Numbering Authority published name Joomla in a form this page reads exactly. Each gives the releases it affects and none names the release that fixes it, so no release is shown as a fix. A record from any other source gives no version here.
No release of a branch that has ended is called safe here. Some of these branches are still named by records published after they ended; the page of each says how many.
Some records give a range with no start: from 0, or before a release. A record is placed on the branch of the release that ends its range. As the record states it, the range also covers every older release. Such a range is not counted when the newest safe release of a branch that still gets fixes is worked out.
Some records give a range that starts in an older branch and ends in a newer one. A record is placed on the branch of the release that ends its range, and as the record states it, the range also covers the older branches it runs across. Only a range that runs across branches that have all ended is placed: a range that reaches a branch that still gets fixes would name that branch's newest release as affected, which a project that also fixes its older branches does not mean. Such a record is named at the end of the page.
5 records are not placed on a branch, so no branch or release row counts them: CVE-2022-23793, CVE-2022-23794, CVE-2022-23795, CVE-2022-23797 and CVE-2022-23798.
Sources
- CVE records: Copyright © 1999-2026, The MITRE Corporation. CVE is a trademark and the CVE logo is a registered trademark of The MITRE Corporation (source). Licence: CVE Program Terms of Use
- Product lifecycle dates from endoflife.date, Copyright 2020 endoflife.date contributors (MIT License) (source). Licence: MIT License
- EPSS scores by FIRST (https://www.first.org/epss/), generated by Empirical Security (source)