CiviCRM 5.48.0, 5.47.4, 5.45.5 ESR Security Release
There has been a security release for CiviCRM. Upgrades are available for:
There has been a security release for CiviCRM. Upgrades are available for:
There has been a security release for CiviCRM. Upgrades are available for:
CiviCRM version 5.20.0 is now out and ready to download.
Important Notice: This is a security release. We recommend you immediately upgrade to one of the following versions:
Below are the security advisories details:
Bugs resolved in 5.19.4:
There has been a security release for CiviCRM. We recommend you immediately upgrade to one of the following versions:
In addition to the security fixes, this release includes several bug fixes.
Below are the security advisories details:
There has been a security release for CiviCRM. We recommend you immediately upgrade to one of the following versions:
Below are the security advisories details:
There has been a security release for CiviCRM. We recommend you immediately upgrade to one of the following versions:
In addition to the security fixes, this release includes two regression fixes.
Below are the security advisories details:
The latest release of CiviCRM 5.3.1 and 4.6.38 includes security fixes. This is a critical security release, we recommend upgrading to 5.3.1 and 4.6.38 to ensure the security of your site and data as soon as possible.
Please note that 4.6.33, 4.7.26, and 4.7.27 are security releases. All releases include the latest security fixes, and 4.7.27 includes additional bug fixes and enhancements (as a typical monthly release).
Please see below links to the security advisories:
Please note that release 4.7.21 and 4.6.29 are security releases. Please see below links to the security advisories:
All sites are strongly encouraged to upgrade to the latest secure versions of CiviCRM: v4.7.14 and v4.6.24.
The latest release of CiviCRM 4.6 and 4.7 includes security fixes. We recommend upgrading to 4.7.7 or 4.6.16 to ensure the security of your site and data. The latest releases include 2 moderately critical fixes. A number of other non-security issues have also been fixed in the latest releases.
The team is super excited to announce that CiviCRM 4.6.9 is now available for downloading AND you can try it out on the 4.6 demo site.
The latest release of CiviCRM 4.6 includes security fixes. While this issue is unlikely to affect the average CiviCRM site, it is recommended to upgrade to the latest version to keep your site as secure as possible.
If you are currently using 4.6.7 and your site uses ACLs to segment access to contacts you are strongly encouraged to upgrade. The 4.6.7 release included a regression in the ACL system which caused certain contact access permissions to behave improperly. The 4.4 LTS branch was unaffected.
The latest releases of CiviCRM 4.6 and 4.4 LTS include 2 moderately critical security fixes. While these issues are unlikely to affect the average CiviCRM site, it is recommended to upgrade to the latest version to keep your site as secure as possible.
IATS has been a payment processor extension with CiviCRM for quite a while and has been actively developed & supported. If you are using the IATS extension you can say a quiet thank you to Alan, Karin & Stephen & stop reading.
An important security update is being released for both the latest version of CiviCRM and the long-term-support version. We recommend you upgrade immediately to maintain the security of your site.
For more information on the security issues see:
The team is pleased to announce the fifth stable release of the incredible CiviCRM 4.5 series. These release include a security fix and a number of other improvements.
The security issue only affects sites using the CiviCase component. Read the security announcement for details.
There has been a security advisory for CiviCRM. We recommend you immediately upgrade to one of the following versions:
Read the security advisories for details:
There has been a security advisory for CiviCRM. We recommend you immediately upgrade to one of the following versions:
Read the security advisories for details:
There has just been a security advisory for CiviCRM. We recommend you immediately upgrade to one of the following newly released versions:
A moderately critical security issue has just been fixed in CiviCRM. We recommend you immediately upgrade to one of the following newly released versions:
Read the following security announcement for details:
A critical security issue has just been fixed in CiviCRM. For the safety of your CiviCRM data you should immediately upgrade to one of the following newly released versions:
The community of developers and implementers is proud to announce the 4.2.10 LTS release of CiviCRM. LTS stands for "long term support" and the purpose of this release is three fold:
1. To provide bug and security fixes to those who are not ready to upgrade to CiviCRM 4.3 just yet
2. To increase the reliability of an existing CiviCRM release
Announcing the 6th stable release of CiviCRM 4.3, containing small bug fixes and two minor security updates to make your CRM more stable and secure.
This is a security release. You should upgrade your site immediately. If you are unable to do so, read the following security bulletins for alternate instructions for securing your site:
SECURITY Fixes in 4.3.5:
Today marks the 5th stable release of CiviCRM 4.3. The CiviCRM community has truly rallied to make 4.3 the most reliable and feature-rich version yet - over 60 people contributed patches and testing to 4.3.4 alone.
This is a security release. You should upgrade your site immediately. If you are unable to do so, read the following security bulletins for alternate instructions for securing your site:
SECURITY Fixes in 4.3.4:
Recently I was asked to compile a list of all CiviCRM releases since 3.1.0, identifying which were security releases so that we could make sure clients' sites were secure. The organization I work for (Freeform Solutions) is focused on doing sites for other non-profit organizations, many of whom are still running older versions of CiviCRM due to budgetary or other constraints, so we wanted to be sure that no one was running a version known to contain security vulnerabilities.