Alchemy: Unauthenticated nested page API leaks restricted & unpublished content
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 7.4.15, 8.0.15, 8.1.14, 8.2.6
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: poc
- Automatable: yes
- Technical impact: partial
Summary
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.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: poc · Automatable: yes · Technical impact: partial
- Record last updated
Affected versions
- AlchemyCMS alchemy_cms
fixed in 7.4.15; From 8.0.0 · fixed in 8.0.15; From 8.1.0 · fixed in 8.1.14; From 8.2.0 · fixed in 8.2.6
- alchemy_cmsRubyGems
From 8.2.0 · fixed in 8.2.6
- alchemy_cmsRubyGems
From 8.1.0 · fixed in 8.1.14
- alchemy_cmsRubyGems
From 8.0.0.a · fixed in 8.0.15
- alchemy_cmsRubyGems
fixed in 7.4.15