Summary
OpenReception allows a TENANT_ADMIN to assign the GLOBAL_ADMIN role through a staff role-update request without verifying that the requester already has platform-wide authorization. An attacker with tenant administrator access may therefore escalate privileges and control other tenants, including their users, staff, configuration, and lifecycle settings.
Affected context
The vulnerability occurs in OpenReception deployments where tenant administrators can update staff roles through the affected role-update handler. The handler accepts the GLOBAL_ADMIN role as a schema-valid value but does not separately enforce a policy limiting that assignment to an existing platform administrator. Hosted multi-tenant deployments face a scope-changing escalation across customers, while single-tenant deployments may still expose global administration functions to an unauthorized tenant administrator.
Exploit preconditions
- Attack surface: Authenticated staff or role-management API
- Required access: A valid TENANT_ADMIN identity with permission to submit staff role updates
- Trigger point: A role-update request that assigns GLOBAL_ADMIN to the requester or another colleague
- Why exploitation is possible: Input schema validation accepts the global role, but authorization policy does not verify that only an existing GLOBAL_ADMIN may grant it
- Additional condition: The newly assigned role becomes effective when the affected account receives refreshed authentication state, such as after re-login
Why this happens
The underlying bug is a failure to separate data validation from authorization. The role value is treated as an allowed enum member, and that syntactic acceptance becomes the effective security decision, even though GLOBAL_ADMIN is a platform-wide capability. This maps to CWE-269, Improper Privilege Management, because the application permits a less-privileged tenant-scoped principal to grant or obtain privileges outside its authorized administrative scope.
Potential impact
- A TENANT_ADMIN may gain platform-wide administrative control.
- An attacker could access or modify other tenants' configuration, users, staff records, and operational metadata.
- An attacker could create, modify, or remove tenants and alter tenant lifecycle settings.
- A tenant administrator could promote another account, potentially obscuring the original operator's identity in audit records.
- Hosted deployments could experience cross-customer administrative compromise.
- The vulnerability may enable follow-on attacks against staff accounts or platform controls, although plaintext appointment contents remain subject to the platform's end-to-end encryption model unless separate weaknesses are chained.
General mitigation guidance
Mitigation generally focuses on enforcing authorization policy independently
from schema validation and on preserving tenant boundaries.
Common defensive patterns include:
- Permit GLOBAL_ADMIN assignment only after an explicit server-side check confirms that the requester already holds the required platform-wide authority.
- Treat role changes as privileged operations with policy checks based on the actor, target, tenant scope, and requested transition.
- Apply deny-by-default rules to cross-tenant and platform-wide role assignments.
- Prevent tenant administrators from modifying global roles, tenant lifecycle controls, or unrelated tenant resources.
- Require appropriately protected workflows for high-impact role changes, such as approval, reauthentication, or step-up authorization where suitable.
- Record the acting principal, target account, prior role, new role, tenant scope, and authorization decision in tamper-resistant audit logs.
- Keep authorization decisions server-side and do not rely on client-provided role claims or enum validity.
- Run administrative identities and service components with the least privilege necessary.
How teams detect issues like this
Organizations can identify similar issues through:
- Static analysis and policy checks for role-update handlers that validate enum membership without an actor-authorization decision.
- Code review searches for assignments of global, owner, superuser, or cross-tenant roles from tenant-scoped endpoints.
- Tests that attempt every role transition from each administrative scope, including self-promotion and promotion of another account.
- Authorization regression tests covering hosted multi-tenant and single-tenant deployment models.
- API monitoring for GLOBAL_ADMIN assignments, unusual role transitions, and tenant administrators modifying identities outside their permitted scope.
- Audit-log correlation between role changes, authentication refreshes, and subsequent cross-tenant administrative actions.
- Automated review tools and security policy enforcement in CI can help flag missing privilege-boundary checks.

