Alchemy: Unauthenticated nested page API leaks restricted & unpublished content
AlchemyCMS alchemy_cms
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| alchemy_cms RubyGems |
|
|
AlchemyCMS alchemy_cms
| Product | Affected | Fixed in |
|---|---|---|
| alchemy_cms RubyGems |
|
|
Alchemy is an open source content management system engine written in Ruby on Rails. Prior to 7.4.15, 8.0.15, 8.1.14, and 8.2.6, the unauthenticated GET /api/pages/nested endpoint implemented by Api::PagesController#nested in app/controllers/alchemy/api/pages_controller.rb returns an unfiltered page tree because it performs no authorization and does not scope descendants by the caller's ability. Anonymous callers can retrieve restricted and unpublished page metadata that the sibling show action denies. When elements=true is supplied, PageTreeSerializer also returns element and ingredient content from restricted pages because PageTreePreloader and the serializer do not apply an ability check to those records. This issue is fixed in versions 7.4.15, 8.0.15, 8.1.14, and 8.2.6.
From the CVE record · GitHub_M
The unauthenticated GET /api/pages/nested endpoint returns a page tree without checking access permissions. An anonymous network caller can retrieve restricted and unpublished page metadata, and can also retrieve element and ingredient content from restricted pages by supplying elements=true. No user interaction is required.
Teams running the RubyGems alchemy_cms package in versions >=8.2.0 <8.2.6, >=8.1.0 <8.1.14, >=8.0.0.a <8.0.15, or <7.4.15 should check their installations.