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

CVE-2026-113653: ApostropheCMS Information Disclosure Flaw

CVE-2026-113653 is an information disclosure vulnerability in ApostropheCMS that exposes user data through public relationships. This post covers technical details, affected versions, security impact, and mitigation steps.

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-113653 Overview

CVE-2026-113653 is an authorization vulnerability in ApostropheCMS, an open-source Node.js content management system. In versions prior to 4.33.0, the viewRole permission check is not applied to anonymous visitors when a developer exposes user objects through a publicly rendered relationship or an explicitly enabled public API. Inadequately scoped templates that serialize an entire related user object can conditionally disclose user fields to unauthenticated requesters. Relationships do not automatically publish full user objects, and password hashes are stored separately and are not affected. The flaw is tracked as [CWE-863: Incorrect Authorization] and is fixed in ApostropheCMS 4.33.0.

Critical Impact

Anonymous visitors may read user object fields when developers expose users through public relationships or APIs, resulting in limited information disclosure of account metadata.

Affected Products

  • ApostropheCMS versions prior to 4.33.0
  • Node.js applications built on the Apostrophe @apostrophecms/apostrophe package
  • Public-facing sites that render user relationships or expose public user APIs

Discovery Timeline

  • 2026-10-20 - CVE-2026-113653 published to NVD
  • 2026-10-20 - Last updated in NVD database
  • ApostropheCMS 4.33.0 - Vendor releases security patch and publishes advisory GHSA-xf6w-q65w-4f2w

Technical Details for CVE-2026-113653

Vulnerability Analysis

The vulnerability stems from incomplete enforcement of role-based authorization in ApostropheCMS's permission model. ApostropheCMS defines a viewRole that gates visibility of user object fields based on the requester's role. For authenticated sessions, the role check restricts which fields a requester can read. For anonymous visitors, the check is not applied in all code paths. When a developer configures a relationship to include a user, or explicitly enables a public API that serializes a user object, the response can include fields that should remain internal to privileged roles.

Password hashes are stored in a separate collection and are not exposed by this flaw. The disclosure is bounded by what the developer has chosen to publish and by the default relationship behavior, which does not automatically serialize full user records.

Root Cause

The root cause is an authorization gap: viewRole was not consistently evaluated for anonymous requesters along code paths that render relationship data or respond to publicly enabled APIs. The CMS treated the absence of a session as implicit public access rather than applying the role filter that strips restricted user fields. This is a classic [CWE-863] incorrect authorization pattern where the policy exists but is not applied uniformly to every actor type.

Attack Vector

Exploitation requires no authentication, no user interaction, and is reachable over the network. An attacker browses a page or calls a public API endpoint on a site where a developer has either (a) rendered a relationship template that serializes the related user object, or (b) explicitly enabled a public API that returns user documents. The response may contain user fields that were intended to be gated behind viewRole.

No working exploit, proof-of-concept URL, or CISA KEV listing is published for this CVE.

text
// Reference patch metadata from the ApostropheCMS repository.
// See: https://github.com/apostrophecms/apostrophe/commit/f84fd41cbf6c22eb8d0008fc9c25df1f7130b350
// See: https://github.com/apostrophecms/apostrophe/commit/9500b8b0e1d630d5e07fbb5fd2c25ed0943845ce
// Fix released in @apostrophecms/apostrophe 4.33.0

Source: GitHub Security Advisory GHSA-xf6w-q65w-4f2w

Detection Methods for CVE-2026-113653

Indicators of Compromise

  • Anonymous HTTP requests to Apostrophe public API routes that return JSON containing user document fields such as username, email, or role metadata.
  • Rendered HTML pages where relationship blocks include user object properties beyond display name or avatar.
  • Access log patterns showing scraping of paginated public endpoints that resolve related users.

Detection Strategies

  • Review ApostropheCMS project source for templates that iterate over _user or similar relationship fields and serialize full objects.
  • Audit module configurations for apiPublic or equivalent flags that expose user-backed document types without a projection filter.
  • Compare installed @apostrophecms/apostrophe version against 4.33.0 across all deployments using software bill of materials (SBOM) tooling.

Monitoring Recommendations

  • Alert on sudden spikes in anonymous requests to API endpoints that return user-type documents.
  • Log and inspect JSON response payloads from Apostrophe routes for fields outside the intended public projection.
  • Track outbound crawler and bot activity against pages that render user relationships, including unusual user-agent strings and high request rates.

How to Mitigate CVE-2026-113653

Immediate Actions Required

  • Upgrade @apostrophecms/apostrophe to version 4.33.0 or later across all ApostropheCMS deployments.
  • Inventory custom modules and templates to identify any public exposure of user objects through relationships or apiPublic configurations.
  • Restrict public API access to user-backed document types until the upgrade is validated in staging.

Patch Information

The fix is included in ApostropheCMS release apostrophe@4.33.0. Relevant commits are f84fd41cbf6c22eb8d0008fc9c25df1f7130b350 and 9500b8b0e1d630d5e07fbb5fd2c25ed0943845ce. Review the Apostrophe 4.33.0 release notes and the GHSA-xf6w-q65w-4f2w advisory for vendor guidance.

Workarounds

  • Remove user object serialization from publicly rendered relationship templates and expose only non-sensitive display fields.
  • Disable any explicitly enabled public APIs that return user documents until the patched version is deployed.
  • Apply response-layer field projections or a reverse proxy filter to strip restricted user fields from anonymous responses as an interim control.
bash
# Upgrade ApostropheCMS to the patched release
npm install @apostrophecms/apostrophe@4.33.0

# Verify installed version
npm ls @apostrophecms/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.