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 filtering leads to XSS vulnerability.
Joomla! version 1.6.3 and all earlier 1.6.x versions
Upgrade to the latest Joomla! version (1.6.4 or later)
The JSST at the Joomla! Security Centre.
When a user requests a password reset, the reset tokens were stored in plain text in the database. While this is not a vulnerability in itself, it allows user accounts to be compromised if there is an extension on the site with an SQL injection vulnerability.
All 1.5.x installs prior to and including 1.5.15 are affected.
Upgrade to the latest Joomla! version (1.5.16 or later)
The JSST at the Joomla! Security Centre.
Session id doesn't get modified when user logs in. A remote site may be able to forward a visitor to the Joomla! site and set a specific cookie. If the user then logs in, the remote site can use that cookie to authenticate as that user.
All 1.5.x installs prior to and including 1.5.15 are affected.
Upgrade to the latest Joomla! version (1.5.16 or later)
The JSST at the Joomla! Security Centre.
The migration script in the Joomla! installer does not check the file type being uploaded. If the installation application is present, an attacker could use it to upload malicious files to a server.
All 1.5.x installs prior to and including 1.5.15 are affected.
Upgrade to the latest Joomla! version (1.5.16 or later)
The JSST at the Joomla! Security Centre.
If a user entered a URL with a negative query limit or offset, a PHP notice would display revealing information about the system.
All 1.5.x installs prior to and including 1.5.15 are affected.
Upgrade to the latest Joomla! version (1.5.16 or later)
The JSST at the Joomla! Security Centre.
It is possible to read the contents of an extension's XML file and find the version number of the installed extension. This could allow people to exploit a known security flaws for a specific version of an extension.
All 1.5.x installs prior to and including 1.5.14 are affected.
Turn on Apache mod_rewrite and configure your .htaccess file to filter out XML files. In the htaccess.txt file shipped with version 1.5.15, lines 35-39 contain example code that will deny access to XML files. You can incorporate this code (or similar code) into your .htaccess file. Be sure to test that it does not cause problems on your site.
The JSST at the Joomla! Security Centre.
When logged into the front end with Author access, it was possible to replace an article written by another user.
All 1.5.x installs prior to and including 1.5.14 are affected.
Upgrade to latest Joomla! version (1.5.15 or newer).
The JSST at the Joomla! Security Centre.
Some files were missing the check for JEXEC. These scripts will then expose internal path information of the host.
All 1.5.x installs prior to and including 1.5.12 are affected.
Upgrade to latest Joomla! version (1.5.13 or newer).
The JSST at the Joomla! Security Centre.
In com_mailto, it was possible to bypass timeout protection against sending automated emails.
All 1.5.x installs prior to and including 1.5.13 are affected.
Upgrade to latest Joomla! version (1.5.14 or newer).
The JSST at the Joomla! Security Centre.
Tiny browser included with TinyMCE 3.0 editor allowed files to be uploaded and removed without logging in.
Version 1.5.12 only
Upgrade to latest Joomla! version (1.5.13 or newer).
The JSST at the Joomla! Security Centre.