This feed provides announcements of resolved security issues in Joomla! software releases.
For more information about the Joomla! Security Strike Team (JSST) and its processes, please review our Security article.
To report potential security issues, please follow the guidelines in the above referenced article. Please note that we are only able to provide support for the Joomla! CMS, Joomla! Framework, and *.joomla.org network of websites.
You can subscribe to notifications from this feed through a RSS reader.
A missing token check causes a CSRF vulnerability in data download endpoints in com_banners and com_sysinfo.
Joomla! CMS versions 3.0.0 - 3.9.26
Upgrade to version 3.9.27
The JSST at the Joomla! Security Centre.
A missing token check causes a CSRF vulnerability in the AJAX reordering endpoint.
Joomla! CMS versions 3.0.0 - 3.9.26
Upgrade to version 3.9.27
The JSST at the Joomla! Security Centre.
HTML was missing in the executable block list of MediaHelper::canUpload, leading to XSS attack vectors.
Joomla! CMS versions 3.0.0 - 3.9.26
Upgrade to version 3.9.27
The JSST at the Joomla! Security Centre.
Inadequate filters on module layout settings could lead to an LFI.
Joomla! CMS versions 3.0.0 - 3.9.25
Upgrade to version 3.9.26
The JSST at the Joomla! Security Centre.
Inadequate escaping allowed XSS attacks using the logo parameter of the default templates on error pages.
Joomla! CMS versions 3.0.0 - 3.9.25
Upgrade to version 3.9.26
The JSST at the Joomla! Security Centre.
Missing input validation within the template manager.
Joomla! CMS versions 3.2.0 - 3.9.24
Upgrade to version 3.9.25
The JSST at the Joomla! Security Centre.
Usage of the insecure rand() function within the process of generating the 2FA secret.
Usage of an insufficient length for the 2FA secret accoring to RFC 4226 of 10 bytes vs 20 bytes.
Additional details as well as a more contexts for exising sites can be found in the docs: https://docs.joomla.org/J3.x:Changes_to_the_2FA_token_generation_recommendations_for_existing_sites
This issue has been coordinated with Akeeba Ltd as contributor of the original FOF codebase to the core.
Joomla! CMS versions 3.2.0 - 3.9.24
Upgrade to version 3.9.25
The JSST at the Joomla! Security Centre.
The core shipped but unused randval implementation within FOF (FOFEncryptRandval) used an potential insecure implemetation. That has now been replaced with a call to "random_bytes()" and its backport that is shipped within random_compat.
This issue has been coordinated with Akeeba Ltd as contributor of the original FOF codebase to the core.
Joomla! CMS versions 3.2.0 - 3.9.24
Upgrade to version 3.9.25
The JSST at the Joomla! Security Centre.
Missing filtering of messages showed to users that could lead to xss issues.
Joomla! CMS versions 2.5.0 - 3.9.24
Upgrade to version 3.9.25
The JSST at the Joomla! Security Centre.
Extracting an specifilcy crafted zip package could write files outside of the intended path.
Joomla! CMS versions 3.0.0 - 3.9.24
Upgrade to version 3.9.25
The JSST at the Joomla! Security Centre.