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-112952 Overview
CVE-2026-112952 is an information disclosure vulnerability in ApostropheCMS, an open-source Node.js content management system. The flaw exists in the POST /api/v1/@apostrophecms/doc/slugTaken endpoint, which returns a boolean indicating whether a given slug is in use. The endpoint applies no permission check, type filter, or visibility filter. Any authenticated user, including low-privileged editors, can enumerate slugs across private pages, drafts, and archived documents. The issue is tracked under CWE-200: Exposure of Sensitive Information and is fixed in ApostropheCMS version 4.34.0.
Critical Impact
Authenticated users can enumerate the slug namespace of non-public, draft, and archived content, exposing document existence and naming conventions that should remain restricted.
Affected Products
- ApostropheCMS versions prior to 4.34.0
- Node.js deployments using the @apostrophecms/doc module with the slugTaken endpoint exposed
- Multi-tenant ApostropheCMS instances where editors should not observe private content metadata
Discovery Timeline
- 2026-10-20 - CVE-2026-112952 published to the National Vulnerability Database (NVD)
- 2026-10-21 - Last updated in NVD database
Technical Details for CVE-2026-112952
Vulnerability Analysis
The vulnerability resides in the slugTaken API handler within the @apostrophecms/doc module. When a client submits POST /api/v1/@apostrophecms/doc/slugTaken with a JSON body of { "slug": "target-slug" }, the server queries the document collection across all document types and visibility states. The response is a single boolean indicating whether the slug exists.
The handler omits two important controls. It does not filter by document type, so slugs tied to restricted content types are included. It also does not evaluate the caller's view permissions, so drafts, archived content, and private pages contribute to the response. An attacker with any authenticated session can issue repeated requests to probe the slug namespace.
Root Cause
The root cause is a missing authorization and visibility filter on the slugTaken lookup. The endpoint was designed to assist editors in avoiding slug collisions, but the backing query treats every document equally, regardless of state or permissions. This is a classic CWE-200 information exposure pattern where a utility endpoint leaks the existence of resources that the caller cannot otherwise observe.
Attack Vector
Exploitation requires only valid credentials and network access to the ApostropheCMS API. An attacker scripts dictionary or wordlist-based requests against the endpoint, recording which slugs return true. The resulting map reveals internal naming conventions, upcoming campaign pages, archived content, and private editorial drafts.
// Patch excerpt from packages/apostrophe/modules/@apostrophecms/area/index.js
// Fields the user may not view (viewPermission) are removed from documents
// before rendering via apos.doc.removeForbiddenFieldsDeep.
async renderDocsAreas(req, within, { inline = false } = {}) {
within = Array.isArray(within) ? within : [];
self.apos.doc.removeForbiddenFieldsDeep(req, within);
let index = 0;
for (const doc of within) {
// ...
}
}
// Source: https://github.com/apostrophecms/apostrophe/commit/40b989b1a9dd23d30029b8ce7668634265cfe5ea
Detection Methods for CVE-2026-112952
Indicators of Compromise
- High-volume POST requests to /api/v1/@apostrophecms/doc/slugTaken from a single authenticated session
- Sequential or wordlist-style slug values in request bodies across short time windows
- Editor or low-privilege accounts generating API traffic patterns inconsistent with normal content authoring
Detection Strategies
- Parse web and application logs for repeated calls to the slugTaken endpoint and group by user and source IP
- Flag sessions that exceed a baseline threshold of slugTaken requests per minute
- Correlate slugTaken probing with subsequent attempts to access or request specific documents by slug
Monitoring Recommendations
- Enable verbose request logging on the ApostropheCMS reverse proxy or application tier for /api/v1/@apostrophecms/doc/* paths
- Alert on authenticated API clients whose request-rate distribution shifts toward enumeration-shaped patterns
- Review audit trails of editor accounts for unexpected use of utility endpoints outside of the admin UI
How to Mitigate CVE-2026-112952
Immediate Actions Required
- Upgrade ApostropheCMS to version 4.34.0 or later across all environments
- Review editor and contributor account inventories and revoke unused credentials
- Audit recent API logs for signs of slug enumeration prior to patching
Patch Information
The fix is delivered in ApostropheCMS Release v4.34.0. The relevant source changes are in commits 06e4b37 and 40b989b, and the vendor advisory is published as GHSA-f66c-mpj2-3r8h. The patch introduces apos.doc.removeForbiddenFieldsDeep so that fields a user cannot view are stripped from documents before rendering, and tightens related permission handling.
Workarounds
- Restrict access to /api/v1/@apostrophecms/doc/slugTaken at the reverse proxy to administrator accounts only until the upgrade is applied
- Apply rate limiting on the endpoint to slow enumeration attempts
- Rotate shared editor credentials and enforce multi-factor authentication for all CMS logins
# Example NGINX rule to limit slugTaken endpoint access to admins and apply rate limiting
limit_req_zone $binary_remote_addr zone=slugtaken:10m rate=5r/m;
location = /api/v1/@apostrophecms/doc/slugTaken {
limit_req zone=slugtaken burst=3 nodelay;
allow 10.0.0.0/24; # admin subnet
deny all;
proxy_pass http://apostrophe_backend;
}
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

