Summary
Alchemy CMS exposes an unauthenticated page-tree API endpoint that does not enforce authorization or filter results according to the caller's permissions. Anonymous users may retrieve restricted or unpublished page metadata, and requests including element data may also expose content from protected pages.
Affected context
The issue occurs in Alchemy CMS deployments that expose the nested pages API endpoint and rely on its response for page-tree data. The endpoint may return restricted or unpublished pages because it does not apply the same ability checks as related page actions; requesting element data can further expose associated elements and ingredients.
Exploit preconditions
- Attack surface: The HTTP API, specifically the nested pages endpoint
- Required access: No authentication may be required
- Trigger point: An unauthenticated GET request to the page-tree endpoint, optionally requesting element data
- Why exploitation is possible: The controller and related serialization paths do not scope descendants and associated records by the requesting caller's authorization ability
Why this happens
The vulnerability results from missing authorization enforcement in an API endpoint that returns hierarchical records. The controller retrieves a page tree without applying the caller's ability, while preloading and serialization of related elements and ingredients also omit equivalent access checks. This maps to CWE-862: Missing Authorization, where a protected operation or resource is accessible without verifying whether the requester is permitted to view it.
Potential impact
- Anonymous users may discover restricted or unpublished page metadata
- Sensitive page structure and navigation information could be exposed
- Element and ingredient content from protected pages may be disclosed
- Attackers could use exposed content to support reconnaissance or targeted attacks
General mitigation guidance
Mitigation generally focuses on enforcing authorization consistently at every API and serialization boundary.
Common defensive patterns include:
- Applying ability checks before selecting pages and descendants for API responses
- Filtering associated elements and ingredients according to the same authorization policy
- Using secure-by-default response serializers that exclude protected records unless explicitly permitted
- Treating unpublished and restricted content as untrusted for anonymous access
- Centralizing authorization rules and applying least-privilege defaults to API resources
- Adding regression tests for anonymous, authenticated, restricted, and unpublished content access
How teams detect issues like this
Organizations can identify similar issues through:
- Static analysis and policy checks for controller actions that query records without authorization calls
- Code review of API endpoints, serializers, preloaders, and nested-resource traversal
- Tests confirming that anonymous and low-privilege users cannot retrieve restricted or unpublished records
- Monitoring anonymous requests for unusual enumeration of page-tree endpoints or content identifiers
- Automated security review tools that flag resource access paths lacking explicit authorization enforcement

