Applies to CiviCRM 6.20.0 and earlier, all CMSes including Joomla Published for the 18 Nov 2026 announcement

The CiviCRM 6.20.1 security release was announced on 18 November 2026, together with 6.16.9 for the ESR line. It fixes 29 security advisories, five of them rated Critical, and every CiviCRM version up to 6.20.0 is affected. If your Joomla site runs CiviCRM, update to 6.20.1. Sites with public Form Builder forms, profile forms or Search Kit displays should do it first, because five of the advisories name visitors who are not logged in.

What CiviCRM 6.20.1 fixes

AffectedCiviCRM 6.20.0 and earlier
Fixed in6.20.1, 6.16.9 (ESR), and every later release
Advisories29: CIVI-SA-2026-53 to CIVI-SA-2026-81
Risk5 Critical · 23 Moderately critical · 1 Less critical
Types22 access bypass · 3 SQL injection · 3 cross-site scripting · 1 information disclosure

The only solution the advisories give is to upgrade. As of 19 November 2026 there is no hotfix extension to buy time with, unlike the 6.17.1 release in August. The Joomla version doesn't matter: all of this is in CiviCRM itself.

The 29 advisories by area

AreaWhat they are
Form Builder (Afform) · 16Access bypasses in prefill, submissions, autocomplete, file upload fields, group subscriptions, page tokens, contact deduplication and relationship permissions, plus two XSS issues. Four of the five Critical ratings are here (SA-63, 66, 73, 81).
SQL injection · 3CiviReport filters (SA-53), search filters (SA-59), group and campaign filters (SA-62).
APIv4 · 2Contact facade entities (SA-79, Critical) and workflow message rendering (SA-57).
Search Kit · 2A filter bypass when one display is placed twice on a form (SA-77) and XSS in the tag merge alert (SA-78).
CiviContribute · 2Batch entry form (SA-54) and contribution invoices (SA-80).
Contacts, ACLs, profiles, custom search · 4Bulk delete (SA-56), an ACL cache collision (SA-55), public profile forms (SA-60), the Random Segment custom search (SA-61).

The full list with links is in CiviCRM's release announcement.

Which Joomla sites should update first

Five advisories say outright that an unauthenticated visitor could use the bug. All five need something public on your site:

  • Public profile forms (SA-60): custom field values of other records could be shown.
  • Public Form Builder forms (SA-67, 70, 72): reading data of other contacts through prefill, processing pending submissions, and unsubscribing contacts from groups.
  • Search Kit displays on public forms (SA-77): filter restrictions could be bypassed.

Classic contribution and event pages are not Form Builder forms, but they can embed profiles. Sign-up, contact and search forms built in Form Builder are the ones to look for.

A site where only logged-in staff use CiviCRM is less exposed, but do not read the rest as safe. Seven of the remaining advisories name a logged-in user or a specific permission. The others, including the five Critical ones and the three SQL injections, do not say who can exploit them.

Check your version and your public forms

The version is shown in the footer of every CiviCRM admin page and under Administer → Administration Console → System Status. From the shell, with cv:

# run in the Joomla site root
cv ev 'echo CRM_Utils_System::version();'

To see which Form Builder forms are open to visitors, open Administer → Customize Data and Screens → FormBuilder, click Edit on a form and look at Permission in the form settings. Or list all of them, submission forms and search forms:

# run in the Joomla site root
cv api4 Afform.get +s name,title,type,permission,server_route

In the output, *always allow* is the permission the editor calls "Generic: Allow all users (including anonymous)". A form with any permission that Joomla's Public group has is public too. Then check the Joomla side: menu items that point to CiviCRM profile pages, and any page that embeds a form or a Search Kit display.

How to update CiviCRM on Joomla

This is our normal CiviCRM update routine for Joomla, done sooner than usual:

  1. Back up the Joomla files, the database (both databases, if CiviCRM has its own) and the two civicrm.settings.php files.
  2. Refresh staging from live, with email blocked and payments in test mode.
  3. Download the Joomla package from civicrm.org/download. The one listed for Joomla 5 and later is civicrm-6.20.1-joomla5bc.zip.
  4. Unzip it into tmp/ on the server and install the tmp/com_civicrm folder through Install from Folder. Then clear media/civicrm/templates_c.
  5. Run the database upgrade and flush the caches.
  6. Test (next section), then repeat on live in a quiet hour with cron paused.
# run in the Joomla site root, after installing the new package
cv upgrade:db
cv flush

Without shell access, open administrator/index.php?option=com_civicrm&task=civicrm/upgrade&reset=1 instead. If you would rather hand this over, our CiviCRM upgrade service does the staging update and the tests below.

How big the jump is depends on where you start:

  • From 6.20.0: small. The 6.20.1 release notes say no schema change and no API change, only security fixes and seven bug fixes.
  • From 6.19 or older: you also cross the 6.20.0 feature release, which changes the database schema and the API. Read its release notes and plan a real staging test. CiviCRM's previous security release, 6.19.3, shipped on 28 October.
  • On ESR: 6.16.9 is for ESR subscribers. A site on 6.16 without the subscription has to move to 6.20.1.

Check PHP while you are there. CiviCRM's requirements page recommends PHP 8.3, 8.4 or 8.5 for 6.16 and later, and PHP 8.2 reaches end of life on 31 December 2026. Our PHP 8.2 end-of-life plan for Joomla covers that move.

What to test after the update

Most fixes tighten permission checks in Form Builder, Search Kit and APIv4. The likely side effect is a form or a list that worked before because a check was too loose. Test these on staging, logged out and logged in:

  • Every public Form Builder form: open it, submit it, and check the confirmation message and the redirect (SA-63 changed how tokens are handled there).
  • Forms that prefill data for a logged-in contact, or through a link sent by email.
  • Forms that update an existing contact through a dedupe rule: a matching rule no longer overwrites an identified contact or removes its email, phone or address (SA-64, 68).
  • Forms that create relationships, quick-add forms, and forms whose submissions wait for review or email verification (SA-70, 74, 76, 81).
  • Forms with file upload fields, autocomplete fields or a group subscription.
  • Search Kit displays embedded in forms and on public pages: do the filters still return what you expect?
  • Sites that use ACLs: log in as a restricted user and compare which contacts are visible. The ACL fix changes how allow and deny rules are applied (SA-55), and bulk delete now needs edit permission (SA-56).
  • Integrations and custom extensions that call APIv4, especially ones that update Individual, Organization or Household records.
  • CiviReport instances with saved filters, and scheduled reminders that use group or campaign filters.
  • Contribution invoices from the contact dashboard, and batch entry if your finance team uses it.

Then run the short version of our donation, membership and event checklist: one donation, one sign-up, one test mailing, one cron run.

If you cannot update today

As of 19 November 2026 there is no official workaround, so anything short of the update only reduces exposure. Unpublishing a Joomla menu item is not one of those things: it hides the link, but the CiviCRM form behind it still answers. What does reduce exposure while staging is being prepared:

  • Form Builder forms: change the permission of non-essential public forms from "Allow all users" to a logged-in permission, or disable the form.
  • Profiles: in the CiviCRM component's Joomla permissions (Options → Permissions), remove "CiviCRM: profile create" and "CiviCRM: profile view" from the Public group. Check first which contribution and event pages embed a profile, because they depend on the same permissions.

Write down what you changed so you can put it back after the update.