Some permissions were not being checked adequately before returning results from the CiviCRM APIv4. This did not affect everyday use of CiviCRM, but an attacker could potentially exploit this to bypass security checks and read private data from the database. To date there are no known sites that have been compromised due to this bug. APIv3 was not affected.
The CiviCRM Community Council and CiviCRM Core Team are putting together quarterly meetings and invite you to attend. Dubbed ‘Community Round Tables’, these online meetings are intended to provide attendees with general project updates as well as an opportunity for Q&A and general feedback with the Community Council, the Core Team, and community members at large.
The Community Round Tables will include 2 meetings every quarter in order to accommodate users around the world, with the first happening on April 20th. Information and registration online:
As you may be aware, CiviCRM was recently given an award for its incredible social impact by the Free Software Foundation. I think we can all agree that CiviCRM is amazing software! Likewise, I believe that we all recognize that our diversity in perspectives, nationalities, genders, text editors, etc. is vital to the health of both the software and the project.
I’m writing this blog post because now may be one of those times where, as a member of our diverse community, you may wish to express your individual views.
Coleman Watts of the CiviCRM Core Team will give a webinar to present new developments in SearchKit and FormBuilder on April 7 @ 11am US Eastern Time (4pm BST). The webinar will include time for Q&A on planned developments for both SearchKit and Form Builder.
Update: The recording is now available here:
(This is a public service announcement related to security functionality. It does not detail an exploitable vulnerability. Rather, we wish to advise administrators and developers about an on-going change to improve security.)
CiviCRM v3.1 introduced a helper "CRM_Utils_Crypt" which encrypted the SMTP password. This mechanism is being phased-out circa 5.34 in favor of a more secure mechanism. We will briefly consider the purpose of the mechanism, some of its issues, and the details of the change.
In the Joomla integration, some references to user-account records were not properly sanitized.
CiviCRM's REST API traditionally requires two keys, the "API Key" and the "Site Key". The "Site Key" could potentially be extracted by a "timing attack". In this scenario, an attacker would send many invalid requests, build a statistical profile, and infer the most likely value.
The introduction text on a Personal Campaign Page (PCP) was not properly sanitised prior to display on the Personal Campaign page.
When generating the example code in the APIv4 Explorer, the user entered data was not properly sanitised before displaying as example code within the Explorer.
The "Manage Extensions" screen provides a list of extensions published by third-party developers. If an extension had a malicious description, it could trick the user's browser into executing Javascript code.
Note: To exploit this, an attacker would need to gain control of a trusted developer account, and they would leave evidence in a public feed. At time of writing, there is no known evidence of previous attack. Resolving this issue prevents future attacks.
