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 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.