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.
The debug views of com_users do not properly escape user supplied data, which leads to a potential XSS attack vector.
Joomla! CMS versions 1.7.0 through 3.9.5
Upgrade to version 3.9.6
The JSST at the Joomla! Security Centre.
The $.extend method of JQuery is vulnerable to Object.prototype pollution attacks.
Joomla! CMS versions 3.0.0 through 3.9.4
Upgrade to version 3.9.5
The JSST at the Joomla! Security Centre.
The "refresh list of helpsites" endpoint of com_users lacks access checks, allowing calls from unauthenticated users.
Joomla! CMS versions 3.2.0 through 3.9.4
Upgrade to version 3.9.5
The JSST at the Joomla! Security Centre.
The Media Manager component does not properly sanitise the folder parameter, allowing attackers to act outside the media manager root directory.
Joomla! CMS versions 1.5.0 through 3.9.4
Upgrade to version 3.9.5
The JSST at the Joomla! Security Centre.
The sample data plugins lack ACL checks, allowing unauthorized access.
Joomla! CMS versions 3.8.0 through 3.9.3
Upgrade to version 3.9.4
The JSST at the Joomla! Security Centre.
The media form field lacks escaping, leading to a XSS vulnerability.
Joomla! CMS versions 3.2.0 through 3.9.3
Upgrade to version 3.9.4
The JSST at the Joomla! Security Centre.
The item_title layout in edit views lacks escaping, leading to a XSS vulnerability.
Joomla! CMS versions 3.2.0 through 3.9.3
Upgrade to version 3.9.4
The JSST at the Joomla! Security Centre.
The JSON handler in com_config lacks input validation, leading to XSS vulnerability.
Joomla! CMS versions 3.2.0 through 3.9.3
Upgrade to version 3.9.4
The JSST at the Joomla! Security Centre.
The phar:// stream wrapper can be used for objection injection attacks. We now disallow usage of the phar:// handler for non .phar-files within the CMS globally by implementing the TYPO3 PHAR stream wrapper.
Joomla! CMS versions 2.5.0 through 3.9.2
Upgrade to version 3.9.3
The JSST at the Joomla! Security Centre.
Inadequate parameter handling in JS code could lead to an XSS attack vector.
Joomla! CMS versions 2.5.0 through 3.9.2
Upgrade to version 3.9.3
The JSST at the Joomla! Security Centre.
Inadequate checks at the Global Configuration helpurl settings allowed a stored XSS.
Joomla! CMS versions 2.5.0 through 3.9.2
Upgrade to version 3.9.3
The JSST at the Joomla! Security Centre.
"No Filtering" textfilter overrides child settings in the Global Configuration. This is intended behavior but might be unexpected for the user. An additional message is now shown in the configuration dialog.
Joomla! CMS versions 2.5.0 through 3.9.2
Upgrade to version 3.9.3
The JSST at the Joomla! Security Centre.
A combination of specific webserver configurations, in connection with specific file types and browserside mime-type sniffing causes a XSS attack vector.
Joomla! CMS versions 1.0.0 through 3.9.2
Upgrade to version 3.9.3
The JSST at the Joomla! Security Centre.
Inadequate filtering on URL fields in various core components could lead to an XSS vulnerability.
Joomla! CMS versions 2.5.0 through 3.9.2
Upgrade to version 3.9.3
The JSST at the Joomla! Security Centre.
Inadequate checks at the Global Configuration helpurl 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 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.