Skip to content

Joomla! 5.2.1

Compare
Choose a tag to compare
@Hackwar Hackwar released this 07 Nov 17:00
· 98 commits to 5.2-dev since this release
ba684a4

πŸ‘€ Release information

πŸš€ Download information

Note

Userfacing information about this Joomla! release can be found on the release page

πŸ”₯ Installation Packages

New Joomla! Installations SHA-256 Checksums
ZIP Archive (.zip) 2b76165ab78fc923c5ecbe0ddf36605e64086ce50e48e8b844fedd351246fcc6
GNU Zip Archive (.tar.gz) 090db690680346076a0b9e5f051076191829f4d6745ccae243856a94024eada3
Zstandard Archive (.tar.zst) 4cfa9097a1582f6244b45e6fcd660a34b2847229075e6dc760587c220438745c

Additional and a second source of checksums can be found at our official download page. If you need further information on how to validate a release package please visit our documentation.

βœ’οΈ Upgrade Packages

Important

Don't update directly from a version lower than 4.4 it is important that you first update to 4.4 and then update to 5.x

Update from a previous version SHA-256 Checksums
ZIP Archive (.zip) c7e358dd1e5e4d8c1db1de6d41c939ef3fb4002ddac778669689a5f9ecb3c6f5
GNU Zip Archive (.tar.gz) 9c650c854e1f6a864f6466ee6d51f728f9206825163f07e997b6f802908cbb39
Zstandard Archive (.tar.zst) 927ea8dab7663e26af49993f14c10a3229767d252482ef3c7afe12290d463f7c

Additional and a second source of checksums can be found at our official download page. If you need further information on how to validate a release package please visit our documentation.

🧹 What has been changed

Fixing the file permissions for new installations. Due to a packaging error when building the 5.2.0 release, new installations had default file permissions which were too permissive. All files and folders in a new installation had the permissions set to 777, where 755 for folders and 644 for files would have been correct. This might make the installation vulnerable on specific hosting setups. This issue does NOT affect updates to 5.2.0 of existing Joomla sites, as during the update process, Joomla already automatically sets the permissions correctly, overwriting permissions in the archive.

For sites created with the affected 5.2.0 packages, an automated solution updating the permissions of affected files and folders will be shipped with the next regular 5.2.x release. Site owners can either wait for that release or update the permissions manually.