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 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.
com_media allowed paths that are not intended for image uploads.
Joomla! CMS versions 3.0.0 - 3.9.24
Upgrade to version 3.9.25
The JSST at the Joomla! Security Centre.
Incorrect ACL checks could allow unauthorized change of the category for an article.
Joomla! CMS versions 3.0.0 - 3.9.24
Upgrade to version 3.9.25
The JSST at the Joomla! Security Centre.
Inadequate filtering of form contents could allow to overwrite the author field. The affected core components are com_fields, com_categories, com_banners, com_contact, com_newsfeeds and com_tags.
Joomla! CMS versions 1.6.0 - 3.9.24
Upgrade to version 3.9.25
The JSST at the Joomla! Security Centre.
Lack of escaping of image-related parameters in multiple com_tags views cause lead to XSS attack vectors.
Joomla! CMS versions 3.1.0 - 3.9.23
Upgrade to version 3.9.24
The JSST at the Joomla! Security Centre.
Lack of escaping in mod_breadcrumbs aria-label attribute allows XSS attacks.
Joomla! CMS versions 3.9.0 - 3.9.23
Upgrade to version 3.9.24
The JSST at the Joomla! Security Centre.
Lack of ACL checks in the orderPosition endpoint of com_modules leak names of unpublished and/or inaccessible modules.
Joomla! CMS versions 3.0.0 - 3.9.23
Upgrade to version 3.9.24
The JSST at the Joomla! Security Centre.
Lack of input validation while handling ACL rulesets can cause write ACL violations.
Joomla! CMS versions 1.7.0 - 3.9.22
Upgrade to version 3.9.23
The JSST at the Joomla! Security Centre.
A missing token check in the emailexport feature of com_privacy causes a CSRF vulnerability.
Joomla! CMS versions 3.9.0 - 3.9.22
Upgrade to version 3.9.23
The JSST at the Joomla! Security Centre.
Improper handling of the username leads to a user enumeration attack vector in the backend login page.
Joomla! CMS versions 3.9.0 - 3.9.22
Upgrade to version 3.9.23
The JSST at the Joomla! Security Centre.
Improper filter blacklist configuration leads to a SQL injection vulnerability in the backend user list.
Joomla! CMS versions 3.0.0 - 3.9.22
Upgrade to version 3.9.23
The JSST at the Joomla! Security Centre.
The folder parameter of mod_random_image lacked input validation, leading to a path traversal vulnerability.
Joomla! CMS versions 2.5.0 - 3.9.22
Upgrade to version 3.9.23
The JSST at the Joomla! Security Centre.
The globlal configuration page does not remove secrets from the HTML output, disclosing the current values.
Joomla! CMS versions 2.5.0 - 3.9.22
Upgrade to version 3.9.23
The JSST at the Joomla! Security Centre.
The autosuggestion feature of com_finder did not respect the access level of the corresponding terms.
Joomla! CMS versions 2.5.0 - 3.9.22
Upgrade to version 3.9.23
The JSST at the Joomla! Security Centre.
Lack of input validation in com_content leads to an open redirect.
Joomla! CMS versions 3.0.0 - 3.9.20
Upgrade to version 3.9.21
The JSST at the Joomla! Security Centre.
Lack of input validation allows com_media root paths outside of the webroot.
Joomla! CMS versions 2.5.0 - 3.9.20
Upgrade to version 3.9.21
The JSST at the Joomla! Security Centre.