Summary
OpenReception versions before the security fix allow unauthenticated requests to the administrator setup endpoint to create additional active GLOBAL_ADMIN accounts after an instance has already been claimed. An attacker who can submit a request with an accepted same-origin context may gain full platform-level administrative control without email confirmation or other interaction.
Affected context
The vulnerability occurs in fully provisioned OpenReception deployments where the setup page remains reachable after an administrator has claimed and configured the instance. The layout-level protection redirects GET requests, but the form action handling the POST does not recheck whether an administrator already exists, allowing the account-creation operation to remain available.
Exploit preconditions
- Attack surface: The
/setup/create-admin-accountform action - Required access: No OpenReception authentication is required
- Network position: Network access sufficient to submit a request to the deployed instance
- Request condition: The request must satisfy the application's same-origin request check; tools capable of supplying a matching
Originheader may meet this condition - Trigger point: An unauthenticated POST to the administrator creation action
- Why exploitation is possible: The POST handler creates an active GLOBAL_ADMIN account without verifying that an administrator already exists
Why this happens
The underlying defect is an authorization check applied inconsistently across HTTP methods and request handlers. Although the setup page's GET path redirects after initial claiming, the corresponding POST action does not enforce the same state-dependent authorization rule or recheck adminExists() before creating an account. This maps to CWE-862: Missing Authorization, because a sensitive administrative operation lacks an effective authorization control.
Potential impact
- An attacker may create one or more active GLOBAL_ADMIN accounts
- An attacker could obtain full platform-level administrative control
- Tenant information and account data may be exposed or modified
- Appointment and platform configuration could be altered or disrupted
- Administrative privileges may enable further compromise of connected services or data
General mitigation guidance
Mitigation typically focuses on enforcing authorization at the operation boundary rather than relying on page-level or GET-only protections.
Common defensive patterns include:
- Require an authenticated, authorized administrator for account-creation actions after initial setup
- Enforce a server-side invariant that prevents additional GLOBAL_ADMIN creation once an instance is claimed
- Apply the same authorization and state checks consistently to GET, POST, and alternate invocation paths
- Use secure-by-default setup flows that close or disable provisioning endpoints after initialization
- Reduce trust in client-supplied request context and validate origin, session, and authorization state server-side
- Apply least privilege to administrative roles and separate initial provisioning from routine administration
- Add rate limiting, audit events, and alerting for privileged-account creation attempts
- Use a vendor-maintained patched release that includes the authorization correction
How teams detect issues like this
Organizations can detect this class of issue through:
- Static analysis rules identifying sensitive POST handlers without authentication or authorization checks
- Code review checks for authorization enforced only in layouts, routes, or GET handlers
- Tests that attempt privileged state-changing operations before and after initial setup
- Policy enforcement requiring server-side checks for account creation, role assignment, and provisioning endpoints
- Monitoring for unexpected GLOBAL_ADMIN creation, repeated setup requests, and privileged account changes
- Automated security review tools that identify unauthenticated administrative actions and missing state invariants

