The issue concerns token reuse in invitation URLs, leading to access control bypass via the use of a different enrollment flow than the one provided. An attacker who knows different invitation flows names, such as `enrollment-invitation-test` and `enrollment-invitation-admin`, can signup via a single invitation URL for any valid invite link received. This is possible because the token used in the `Invitations` section of the Admin interface does not change when a different `enrollment flow` is selected, and it is not bound to the selected flow. Only configurations that use invitations and have multiple enrollment flows with invitation stages that grant different permissions are affected. The default configuration and configurations with a single enrollment flow are not vulnerable.