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 checks at the Global Configuration Text Filter settings allowed a stored XSS.
Joomla! CMS versions 2.5.0 through 3.9.1
Upgrade to version 3.9.2
The JSST at the Joomla! Security Centre.
Inadequate escaping in com_contact leads to a stored XSS vulnerability
Joomla! CMS versions 2.5.0 through 3.9.1
Upgrade to version 3.9.2
The JSST at the Joomla! Security Centre.
Inadequate escaping in mod_banners leads to a stored XSS vulnerability.
Joomla! CMS versions 2.5.0 through 3.9.1
Upgrade to version 3.9.2
The JSST at the Joomla! Security Centre.
Added additional CSRF hardening in com_installer actions in the backend.
Joomla! CMS versions 2.5.0 through 3.8.12
Upgrade to version 3.8.13
The JSST at the Joomla! Security Centre.
In case that an attacker gets access to the mail account of an user who can approve admin verifications in the registration process he can activate himself.
Joomla! CMS versions 1.5.0 through 3.8.12
Upgrade to version 3.8.13
The JSST at the Joomla! Security Centre.
Inadequate checks on the tags search fields can lead to an access level violation.
Joomla! CMS versions 3.1.0 through 3.8.12
Upgrade to version 3.8.13
The JSST at the Joomla! Security Centre.
Joomla’s com_joomlaupdate allows the execution of arbitrary code. The default ACL config enabled access of Administrator-level users to access com_joomlaupdate and trigger a code execution.
Joomla! CMS versions 2.5.4 through 3.8.12
Upgrade to version 3.8.13
The JSST at the Joomla! Security Centre.
Inadequate checks in com_contact could allowed mail submission in disabled forms.
Joomla! CMS versions 2.5.0 through 3.8.12
Upgrade to version 3.8.13
The JSST at the Joomla! Security Centre.
Inadequate checks regarding disabled fields can lead to an ACL violation.
Joomla! CMS versions 3.7.0 through 3.8.11
Upgrade to version 3.8.12
The JSST at the Joomla! Security Centre.
Inadequate output filtering on the user profile page could lead to a stored XSS attack.
Joomla! CMS versions 1.5.0 through 3.8.11
Upgrade to version 3.8.12
The JSST at the Joomla! Security Centre.
Inadequate checks in the InputFilter class could allow specifically prepared PHAR files to pass the upload filter.
Joomla! CMS versions 1.5.0 through 3.8.11
Upgrade to version 3.8.12
The JSST at the Joomla! Security Centre.
In some cases the link of the current language might contain unescaped HTML special characters. This may lead to reflective XSS via injection of arbitrary parameters and/or values on the current page url.
Joomla! CMS versions 1.6.0 through 3.8.8
Upgrade to version 3.8.9
The JSST at the Joomla! Security Centre.
Our autoload code checks classnames to be valid, using the "class_exists" function in PHP. In PHP 5.3 this function validates invalid names as valid, which can result in a Local File Inclusion.
Joomla! CMS versions 2.5.0 through 3.8.8
Upgrade to version 3.8.9
The JSST at the Joomla! Security Centre.
Inadequate filtering of file and folder names lead to various XSS attack vectors in the media manager.
Joomla! CMS versions 1.5.0 through 3.8.7
Upgrade to version 3.8.8
The JSST at the Joomla! Security Centre.
Under specific circumstances (a redirect issued with a URI containing a username and password when the Location: header cannot be used), a lack of escaping the user-info component of the URI could result in a XSS vulnerability.
Joomla! CMS versions 3.1.2 through 3.8.7
Upgrade to version 3.8.8
The JSST at the Joomla! Security Centre.
A long running background process, such as remote checks for core or extension updates, could create a race condition where a session which was expected to be destroyed would be recreated.
Joomla! CMS versions 3.0.0 through 3.8.7
Upgrade to version 3.8.8
The JSST at the Joomla! Security Centre.
Inadequate filtering allows users authorised to create custom fields to manipulate the filtering options and inject an unvalidated option.
Joomla! CMS versions 3.7.0 through 3.8.7
Upgrade to version 3.8.8
The JSST at the Joomla! Security Centre.
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.