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.
Uploading a file name of an excess length causes the error. This error brings up the screen with the path of the source code of the web application.
Joomla! CMS versions 3.0.0 - 3.10.6 & 4.0.0 - 4.1.0
Upgrade to version 3.10.7 or 4.1.1
The JSST at the Joomla! Security Centre.
A user row was not bound to a specific authentication mechanism which could under very special circumstances allow an account takeover.
Joomla! CMS versions 2.5.0 - 3.10.6 & 4.0.0 - 4.1.0
Upgrade to version 3.10.7 or 4.1.1
The JSST at the Joomla! Security Centre.
Lack of input validation could allow an XSS attack using com_fields
Joomla! CMS versions 3.7.0 - 3.10.6
Upgrade to version 3.10.7
The JSST at the Joomla! Security Centre.
Inadequate filtering on the selected Ids on an request could resulted into an possible SQL injection.
Joomla! CMS versions 3.0.0 - 3.10.6 & 4.0.0 - 4.1.0
Upgrade to version 3.10.7 & 4.1.1
The JSST at the Joomla! Security Centre.
Inadequate validation of URLs could result into an invalid check whether an redirect URL is internal or not.
Joomla! CMS versions 2.5.0 - 3.10.6 & 4.0.0 - 4.1.0
Upgrade to version 3.10.7 & 4.1.1
The JSST at the Joomla! Security Centre.
Under specific circumstances, JInput pollutes method-specific input bags with $_REQUEST data.
Joomla! CMS versions 4.0.0 - 4.1.0
Upgrade to version 4.1.1
The JSST at the Joomla! Security Centre.
Inadequate content filtering leads to XSS vulnerabilities in various components.
Joomla! CMS versions 4.0.0 - 4.1.0
Upgrade to version 4.1.1
The JSST at the Joomla! Security Centre.
Possible XSS attack vector through SVG embedding in com_media.
Joomla! CMS versions 4.0.0 - 4.1.0
Upgrade to version 4.1.1
The JSST at the Joomla! Security Centre.
The media manager does not correctly check the user's permissions before executing a file deletion command.
Joomla! CMS versions 4.0.0
Upgrade to version 4.0.1
The JSST at the Joomla! Security Centre.
Inadequate escaping in the imagelist view of com_media leads to a XSS vulnerability.
Joomla! CMS versions 3.0.0 - 3.9.27
Upgrade to version 3.9.28
The JSST at the Joomla! Security Centre.
Install action in com_installer lack the required hardcoded ACL checks for superusers, leading to various potential attack vectors. A default system is not affected cause by default com_installer is limited to super users already.
Joomla! CMS versions 2.5.0 - 3.9.27
Upgrade to version 3.9.28
The JSST at the Joomla! Security Centre.
Various CMS functions did not properly termine existing user sessions when a user's password was changed or the user was blocked.
Joomla! CMS versions 2.5.0 - 3.9.27
Upgrade to version 3.9.28
The JSST at the Joomla! Security Centre.
Missing validation of input could lead to a broken usergroups table.
Joomla! CMS versions 2.5.0 - 3.9.27
Upgrade to version 3.9.28
The JSST at the Joomla! Security Centre.
Inadequate escaping in the Rules field of the JForm API leads to a XSS vulnerability.
Joomla! CMS versions 3.0.0 - 3.9.27
Upgrade to version 3.9.28
The JSST at the Joomla! Security Centre.
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.
Missing filtering of feed fields 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.