See Registration role - Critical - Access bypass - SA-CONTRIB-2024-015.

This release ensures that, even if configuration does not ever get updated to the new schema as expected, only the expected roles are granted to new registrants.

If you cannot update right away, simply re-save the configuration form at /admin/people/registration-role and your configuration will be fixed, even without this release.

Review user accounts registered between 2023 July 11 and now for having additional roles you did not intend for them to have. If your site missed or reverted an update to configuration in the version 2.0.0 release of Registration Role (or development branch from 2020 August 17 on), non-selected roles were not removed from configuration. Without this update, up until you re-saved the settings form or until you install the new release, whichever came first, users who registered receive all roles, including the Administrator role.

When you run update hooks after this release, it will warn you if the site was affected directly before running update hooks but cannot guarantee that the site was never affected. (If following standard update procedures of running update hooks with the code update and then committing the configuration, then your site was never affected.) Users with all roles should stand out notably in the /admin/people listing— or filter by Administrator role and ensure everyone who has that, should have it.

VCS Label
2.0.1
Release type
Short description
Ensure non-updated configuration does not grant registerers all roles
Packaged Git sha1
5cdb50a61747d117dda45a6c231b61cd5a08494f
Release files
86cce791bacb2be23b35c08e7fd0f4eb
Release file SHA-1 hash
89863e32e49c4097522fd7406160adc42800b314
Release file SHA-256 hash
32b09914909566b9553668988bd242886f162a9c10948a83485f12beef4a3e75
f79d0a5234e1c17fffac857e0ae8015a
Release file SHA-1 hash
fbc76f993f8ca186aec1989467dafa6bed520077
Release file SHA-256 hash
cc7a0582843d97bcc0b569d76c1ef43b0fd9ce0583c0ca9f3fb4307734fb3ad5