CiviCRM "Form Builder" allows an administrator to define custom forms. Forms reference an initial data-record
(such as an "Individual submission form"), and forms may reference related records (such Phone or Email).
If a form provides acccess to related records, then a form-user can steal related records. This reveals the content of the record, and it deprives the original owner of access.
Note: CIVI-SA-2026-45 (Backend) and CIVI-SA-2026-46
(Frontend) are similar, in that both deal with stealing records.
However, they differ in important ways. The backend vulnerabilities affect many entities, but the attacker must
have some baseline permissions (such as access CiviCRM or manage own search_kit). The frontend vulnerabilities
can be exploited anonymously, but they only affect entities that are listed on a public form.
CiviCRM v6.19.2 and earlier
CiviCRM v6.19.3, v6.16.6 (ESR), and later
Upgrade to a fixed version of CiviCRM
If you cannot upgrade, then you may wish to temporarily disable public access to your custom form. For example, set the form "Permission" to "Deny all users". (Restore the original "Permission" after upgrading.)
(Alphabetically) Brian Flett (MAS), Coleman Watts (CiviCRM), Seamus Lee (JMA Consulting)
