The vulnerability exists because multiple functions throughout the Keycloak codebase that handle organization-related features failed to properly check if the 'Organizations' feature was enabled for the current realm. Instead of checking the realm-specific setting, the code often relied on a global feature flag (Profile.isFeatureEnabled) or had no check at all. This allowed authenticated users who were part of an organization to access organization data through user-facing APIs (e.g., the account API) or by requesting an OIDC token with the 'organization' scope, even after an administrator had explicitly disabled the feature for that realm. The patch introduces a centralized Organizations.isEnabled(session) method that correctly checks the realm-level configuration and applies this check to all the affected functions, thus preventing the information disclosure.