Skip to main content
Vulnerability Database/CVE-2026-112957

CVE-2026-112957: ApostropheCMS Information Disclosure Flaw

CVE-2026-112957 is an information disclosure vulnerability in ApostropheCMS that allows editor-level users to bypass access controls and read admin-only content. This article covers technical details, affected versions, and mitigation.

Published:

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

CVE-2026-112957 Overview

CVE-2026-112957 is a missing authorization vulnerability [CWE-862] in ApostropheCMS, an open-source Node.js content management system. The flaw affects the getOne REST endpoint for pages, which fails to apply viewRole type-level restrictions or viewPermission field-level redaction. An editor-level user who knows a document _id can read the full contents of admin-only pages, including privileged fields. The companion getAll endpoint correctly enforces both restrictions, isolating the defect to single-document retrieval. The issue is fixed in ApostropheCMS version 4.34.0.

Critical Impact

Authenticated editor-level users can read admin-only page content and privileged fields through the getOne endpoint, resulting in confidentiality loss for restricted documents.

Affected Products

  • ApostropheCMS versions prior to 4.34.0
  • @apostrophecms/apostrophe npm package (page module)
  • Deployments exposing the pages REST API to editor-role accounts

Discovery Timeline

  • 2026-10-20 - CVE-2026-112957 published to NVD
  • 2026-10-21 - Last updated in NVD database

Technical Details for CVE-2026-112957

Vulnerability Analysis

ApostropheCMS enforces access control at two layers for page documents. The viewRole option restricts an entire document type to specific roles, while viewPermission performs field-level redaction before returning data to the client. In vulnerable releases, the pages getOne REST handler bypasses both checks. The getAll handler applies them correctly, which produces inconsistent authorization behavior across the same resource.

An editor-level account that discovers or guesses a document _id can issue a direct REST request and receive the full document body, including fields that should be hidden. The exposure is limited to confidentiality: no integrity or availability impact is introduced, and the attacker must already possess valid editor credentials.

Root Cause

The root cause is missing authorization logic in the getOne code path of the @apostrophecms/page module. Field-level redaction routines such as apos.doc.removeForbiddenFieldsDeep were not invoked before serializing the response. The patch in commit 40b989b adds this call inside renderDocsAreas and related document paths so forbidden fields are stripped prior to rendering.

Attack Vector

Exploitation is network-based and requires low-privilege authentication as an editor-role user. No user interaction is required. The attacker enumerates or obtains a target document _id, then calls the pages getOne REST endpoint directly. The server returns the admin-only document data without applying viewRole or viewPermission filtering.

javascript
// Patch from commit 40b989b in packages/apostrophe/modules/@apostrophecms/area/index.js
// The fields the user may not view (`viewPermission`) are removed
// from the documents first (see `apos.doc.removeForbiddenFieldsDeep`).
async renderDocsAreas(req, within, { inline = false } = {}) {
  within = Array.isArray(within) ? within : [];
  self.apos.doc.removeForbiddenFieldsDeep(req, within);
  let index = 0;
  // Loop over the docs in the array passed in.
  for (const doc of within) {

Source: ApostropheCMS Commit 40b989b

Detection Methods for CVE-2026-112957

Indicators of Compromise

  • Access log entries showing editor-role sessions calling GET /api/v1/@apostrophecms/page/:id for documents the user did not author.
  • Unexpected volume of single-document page fetches from accounts that rarely interact with admin content.
  • REST responses to editor accounts containing fields normally gated by viewPermission.

Detection Strategies

  • Correlate ApostropheCMS access logs with the user role database to flag getOne calls where the requesting role lacks the document type's viewRole.
  • Compare response payload field sets between getAll and getOne for the same document ID; divergence indicates the vulnerable path was used.
  • Alert on direct _id lookups that bypass the normal navigation flow originating from the CMS UI referer.

Monitoring Recommendations

  • Enable verbose request logging on the @apostrophecms/page module and ship logs to a central analytics platform.
  • Track per-user baselines for admin-page access and alert on deviations from editor accounts.
  • Monitor the installed @apostrophecms/apostrophe package version across environments to confirm patch coverage.

How to Mitigate CVE-2026-112957

Immediate Actions Required

  • Upgrade @apostrophecms/apostrophe to version 4.34.0 or later on all ApostropheCMS instances.
  • Audit editor-role accounts and revoke access for users who no longer require content editing privileges.
  • Review access logs for prior getOne requests against admin-only pages during the exposure window.

Patch Information

The fix ships in ApostropheCMS release 4.34.0. The relevant commits are 06e4b37 and 40b989b, which add apos.doc.removeForbiddenFieldsDeep enforcement across document rendering paths. See the ApostropheCMS Security Advisory GHSA-vh56-5m88-39rq and the ApostropheCMS v4.34.0 release notes for full details.

Workarounds

  • Restrict access to the pages REST API at the reverse proxy or WAF layer so only administrator roles can call getOne on protected document types.
  • Remove or demote editor accounts that do not require page editing privileges until the patch is applied.
  • Avoid storing sensitive data in viewPermission-gated fields on admin-only pages until the upgrade is complete.
bash
# Upgrade ApostropheCMS to the patched release
npm install @apostrophecms/apostrophe@4.34.0
npm ls @apostrophecms/apostrophe
# Restart the Node.js application to load the patched module
pm2 restart apostrophe

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.