Highghsa:GHSA-mqq5-j7w8-2hgh

    alchemy_cms: Missing Authorization (ghsa:GHSA-mqq5-j7w8-2hgh)

    Published Sources: Hersteller

    What is affected, what to do

    Update rubygems/alchemy_cms to version 7.4.15, rubygems/alchemy_cms to version 8.0.15, rubygems/alchemy_cms to version 8.1.14.

    Affected
    • rubygems/alchemy_cms *..<= 7.4.14
    • rubygems/alchemy_cms *..>= 8.0.0.a, <= 8.0.14
    • rubygems/alchemy_cms *..>= 8.1.0, <= 8.1.13
    • rubygems/alchemy_cms *..>= 8.2.0, <= 8.2.5
    Fixed in
    • rubygems/alchemy_cms 7.4.15
    • rubygems/alchemy_cms 8.0.15
    • rubygems/alchemy_cms 8.1.14
    • rubygems/alchemy_cms 8.2.6

    Not sure whether and how you are affected? Ask a question about this vulnerability

    Metrics

    —

    Priority

    No value is available for this vulnerability.

    —

    CVSS v3

    No value is available for this vulnerability.

    —

    EPSS score

    No value is available for this vulnerability.

    Show all metrics
    Severity
    High
    Priority (0–325)

    The priority score is a consolidated metric that condenses several individual signals into a single, action-guiding ranking: technical severity (CVSS), exploitation likelihood (EPSS), known-exploited status (KEV) and the context of the affected asset. The aim is to answer the only truly important question in vulnerability management: what first?

    Read in glossary
    19.20 Methodology
    Exploit maturity

    An exploit is code or a technique that specifically uses a concrete vulnerability to force unintended behaviour — such as executing code or escalating privileges. It is the tool that turns a theoretical flaw into a practical attack.

    Read in glossary
    no public PoC known
    KEV status

    The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.

    Read in glossary
    —
    Published
    CWE

    CWE is a catalogue of typical weakness types in software and hardware — such as flawed input validation, unsafe memory handling or poor authentication. Where a CVE names a concrete vulnerability in a concrete product, a CWE describes the underlying class of defect.

    Read in glossary
    CWE-862

    Classification under NIS2 and CRA

    Rule-based classification from exploitation status and severity. It does not replace a case-by-case assessment.

    NIS2

    NIS2 is EU Directive (EU) 2022/2555 to raise the level of cybersecurity across the Union. It substantially broadens obligations compared with the first NIS directive: more sectors, mandatory risk management, staged reporting duties and personal accountability of senior management.

    Read in glossary
    High technical severity: assess and remediate the vulnerability in vulnerability handling under Art. 21(2)(e) NIS2 and document the decision.
    CRA

    The CRA is EU Regulation (EU) 2024/2847 setting horizontal cybersecurity requirements for „products with digital elements“ — from industrial controllers and software to connected consumer devices. For the first time manufacturers must ensure security across the entire product lifecycle, handle vulnerabilities and provide security updates.

    Read in glossary
    From 11.12.2027, Annex I Part II CRA requires manufacturers of affected products with digital elements to handle vulnerabilities without delay and provide security updates.
    ISO/IEC 27001

    ISO/IEC 27001 is the internationally leading standard for an information security management system (ISMS). It describes a risk-based, process-oriented framework to systematically plan, implement, review and improve information security.

    Read in glossary
    Control A.8.8, management of technical vulnerabilities: assess relevance to your systems, plan remediation and keep evidence.

    Description

    Unauthenticated nested page API leaks restricted & unpublished content

    • Location: app/controllers/alchemy/api/pages_controller.rb:28 (Api::PagesController#nested)
    • Affected version: Alchemy CMS 8.3.0.dev (Rails 8.1.3)

    Description

    The unauthenticated GET /api/pages/nested endpoint returns the full page tree to any anonymous caller, including restricted (member-only) pages and unpublished/draft pages that should be hidden. Appending ?elements=true additionally dumps the element/ingredient content of restricted pages, fully bypassing the access control the sibling show and index actions enforce.

    Root cause

    Api::PagesController#nested calls no authorize! and applies no published/restricted scoping, unlike show (authorize! :show) and index (accessible_by(current_ability, :index)). PageTreePreloader loads page.self_and_descendants unfiltered, and PageTreeSerializer emits every page's metadata (and, with elements, public_version.elements) with no ability check.

    Evidence

    An unauthenticated GET /api/pages/nested returns HTTP 200 with the restricted page ("restricted":true) and an unpublished draft ("public":false); ?elements=true leaks its content (e.g. TOPSECRET_RESTRICTED_BODY_proof123). The same guest hitting GET /api/pages/3 (show) gets HTTP 403 {"error":"Not authorized"}, proving nested returns what show correctly denies.

    Reproduction

    # 1) Metadata leak (guest, no auth)
    curl -s http://localhost:3000/api/pages/nested | python3 -m json.tool | grep -E '"name"|"restricted"|"public"'
    
    # 2) Content leak of restricted page
    curl -s "http://localhost:3000/api/pages/nested?elements=true" | grep -oE 'TOPSECRET_RESTRICTED_BODY_[A-Za-z0-9]+|RESTRICTED_RICHTEXT_[A-Za-z0-9]+'
    
    # 3) Contrast — show denies the same guest
    curl -s -o /dev/null -w "show /api/pages/3 -> HTTP %{http_code}\n" http://localhost:3000/api/pages/3
    

    Suggested fix

    def nested
      @page = Page.find_by(id: params[:page_id]) || Language.current_root_page
      authorize! :show, @page
      preloaded_page = PageTreePreloader.new(page: @page, user: current_alchemy_user, ability: current_ability).call
      render json: PageTreeSerializer.new(preloaded_page, ability: current_ability,
                                          user: current_alchemy_user, elements: params[:elements])
    end
    

    Additionally scope PageTreePreloader's self_and_descendants via accessible_by(current_ability) and gate element emission in PageTreeSerializer#page_elements behind opts[:ability].can?(:show, page).

    Source: GitHub Security Advisories

    Affected products

    The following versions are affected. Older releases of the same product line are also vulnerable unless stated otherwise.

    Affected products
    Affected versionsFixed in
    rubygemsalchemy_cms
    • <= 7.4.14
    • >= 8.0.0.a, <= 8.0.14
    • >= 8.1.0, <= 8.1.13
    • >= 8.2.0, <= 8.2.5
    • 7.4.15
    • 8.0.15
    • 8.1.14
    • 8.2.6

    Weakness classes (CWE)

    • CWE-862Missing Authorization

      Class

      The product does not perform an authorization check when an actor attempts to access a resource or perform an action.

      Entry at MITRE CWE-862