Release News
- Details
Joomla! 3.4.8 is now available. This is a bug fix release for the 3.x series of Joomla This release fixes some bugs related to session management from Joomla 3.4.7. The project understands that many of our users are now on Christmas Holiday's so we would like to emphasise that this release only contains bug fixes and whilst we strongly encourage our users to update as soon as practically possible, this update can be left until after any holidays.
What's in 3.4.8
Joomla 3.4.8 fixes some issues found in the 3.4.7 release on Monday to do with browser sessions. All reported bugs from the 3.4.7 update have been fixed in this release:
- Users were unable to edit or create items after the 3.4.7 update
- Fatal error about connection->stat() not existing on external database connections
- After session timeout users could still navigate the backend but without being able to create/edit items or use pagination/filters
For known issues with the 3.4.8 release, see the Version 3.4.8 FAQ in the documentation site.. Please note that it is expected that you will be logged out as soon as the update is complete.
The Production Leadership Team's goal is to continue to provide regular, frequent updates to the Joomla community. Learn more about Joomla development at the Joomla Developer Network.
- Details
Joomla! 3.4.7 is now available. This is a security release for the 3.x series of Joomla which addresses a critical security vulnerability and one low level security vulnerabilities. We strongly recommend that you update your sites immediately.
This release only contains the security fixes; no other changes have been made compared to the Joomla 3.4.6 release.
What's in 3.4.7
Version 3.4.7 is released to address two reported security vulnerabilities and includes security hardening of the MySQLi driver to help prevent object injection attacks.
The Joomla Security Strike team has been following up on the critical security vulnerability patched last week. Since the recent update it has become clear that the root cause is a bug in PHP itself. This was fixed by PHP in September of 2015 with the releases of PHP 5.4.45, 5.5.29, 5.6.13 (Note that this is fixed in all versions of PHP 7 and has been back-ported in some specific Linux LTS versions of PHP 5.3). The only Joomla sites affected by this bug are those which are hosted on vulnerable versions of PHP. We are aware that not all hosts keep their PHP installations up to date so we are making this release to deal with this issue on vulnerable PHP versions.
Security Issues Fixed
- High Priority - Core - Session Hardening (affecting Joomla 1.5 through 3.4.6) More information »
- Low Priority - Core - SQL Injection (affecting Joomla 3.0.0 through 3.4.6) More information »
Please see the documentation wiki for FAQ’s regarding the 3.4.7 release. It is important to note that due to some session changes you will not be able to edit items until you log out and log back in again. Please note that there has been a backwards compatibility break regarding how session management is handled. If you are using the documented Joomla API you will have no issues. The changes are fully documented in the release documentation.
- Details
A Joomla 3.4.7 release containing a security fix will be published today (Monday 21st December) at approximately 21:00 UTC
The Joomla Security Strike team has been following up on the critical security vulnerability patched last week. Since the recent update it has become clear that the root cause is a bug in PHP itself. This was fixed by PHP in September of this year (2015) with the releases of PHP 5.4.45, 5.5.29, 5.6.13 (N.B. Fixed in all versions of PHP 7 and has been backported in some specific Linux LTS versions of PHP 5.3). The only Joomla sites affected by this bug are those which are hosted on vulnerable versions of PHP. We are aware that not all hosts keep their PHP installations up to date so we are releasing a Joomla Update later today which contains additional protection for those users. We do of course recommend that all users apply this update as soon as possible.
From Joomla 3.4.6, performing an update to the new version is as simple as logging in and clicking an update button. The update version warning notice will be clearly visible as soon as an administrator logs in. Joomla advises that there are Joomla extensions available that can apply updates automatically.
Although no longer supported officially, the Joomla Security Strike Team plans to issue patches for Joomla versions 1.5 and 2.5.
Until the release is out, please understand that we cannot provide any further information.
- Details
Joomla! 3.4.6 is now available. This is a security release for the 3.x series of Joomla which addresses a critical security vulnerability and 4 low level security vulnerabilities. We strongly recommend that you update your sites immediately.
This release only contains the security fixes; no other changes have been made compared to the Joomla 3.4.5 release.
What's in 3.4.6
Version 3.4.6 is released to address four reported security vulnerabilities and includes security hardening of the user password reset system.
Security Issues Fixed
- High Priority - Core - Remote Code Execution (affecting Joomla 1.5 through 3.4.5) More information »
- Low Priority - Core - CRSF Hardening (affecting Joomla 3.2.0 through 3.4.5) More information »
- Low Priority - Core - Directory Traversal (affecting Joomla 3.2.0 through 3.4.5) More information »
- Low Priority - Core - Directory Traversal (affecting Joomla 3.4.0 through 3.4.5) More information »
Please see the documentation wiki for FAQ’s regarding the 3.4.6 release.
- Details
Hello from everyone on PLT! We have been busy over the past weeks testing, and re-testing Joomla 3.5 beta 1. Timelines are always the first thing people want to know; followed with what features will be available.
Timeline update for 3.5
Timelines are a tricky part of planning. Bug fixing can be a challenging task to plan for. Sometimes the answer comes instantly and sometimes we’ll lose days on a single issue. We’ve been working tirelessly on an issue for the last couple weeks. We are adjusting our timeline appropriately.