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.
Inadequate input filtering leads to multiple XSS vulnerabilities. Additionally, the default filtering settings could potentially allow users of the default Administrator user group to perform a XSS attack.
Joomla! CMS versions 3.0.0 through 3.8.7
Upgrade to version 3.8.8
The JSST at the Joomla! Security Centre.
The web install application would autofill password fields after either a form validation error or navigating to a previous install step, and displays the plain text password for the administrator account at the confirmation screen.
Joomla! CMS versions 3.0.0 through 3.8.7
Upgrade to version 3.8.8
The JSST at the Joomla! Security Centre.
Inadequate checks allowed users to see the names of tags that were either unpublished or published with restricted view permission .
Joomla! CMS versions 3.1.0 through 3.8.7
Upgrade to version 3.8.8
The JSST at the Joomla! Security Centre.
Depending on the server configuration, PHAR files might be handled as executable PHP scripts by the webserver.
Joomla! CMS versions 2.5.0 through 3.8.7
Upgrade to version 3.8.8
The JSST at the Joomla! Security Centre.
Inadequate checks allowed users to modify the access levels of user groups with higher permissions.
Joomla! CMS versions 2.5.0 through 3.8.7
Upgrade to version 3.8.8
The JSST at the Joomla! Security Centre.
The lack of type casting of a variable in SQL statement leads to a SQL injection vulnerability in the User Notes list view
Joomla! CMS versions 3.5.0 through 3.8.5
Upgrade to version 3.8.6
The JSST at the Joomla! Security Centre.
The lack of type casting of a variable in SQL statement leads to a SQL injection vulnerability in the Hathor postinstall message.
Joomla! CMS versions 3.7.0 through 3.8.3
Upgrade to version 3.8.4
The JSST at the Joomla! Security Centre.
Inadequate input filtering in the Uri class (formerly JUri) leads to a XSS vulnerability.
Joomla! CMS versions 1.5.0 through 3.8.3
Upgrade to version 3.8.4
The JSST at the Joomla! Security Centre.
Inadequate input filtering in com_fields leads to a XSS vulnerability in multiple field types, i.e. list, radio and checkbox.
Joomla! CMS versions 3.7.0 through 3.8.3
Upgrade to version 3.8.4
The JSST at the Joomla! Security Centre.
Lack of escaping in the module chromes leads to XSS vulnerabilities in the module system.
Joomla! CMS versions 3.0.0 through 3.8.3
Upgrade to version 3.8.4
The JSST at the Joomla! Security Centre.