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-113660 Overview
ApostropheCMS, an open-source Node.js content management system, contains a missing authorization vulnerability in its exist-in-locale API endpoint. Prior to version 4.33.0, an authenticated low-privilege user can query the endpoint to determine whether restricted documents exist within a specified locale and mode, including draft mode. The endpoint returns localized document identifiers without enforcing document-level view or edit authorization checks. This issue is tracked as [CWE-862: Missing Authorization] and was fixed in ApostropheCMS 4.33.0.
Critical Impact
Authenticated low-privilege users can enumerate restricted document identifiers across locales and draft mode, exposing the existence of content they are not authorized to access.
Affected Products
- ApostropheCMS versions prior to 4.33.0
- ApostropheCMS exist-in-locale API endpoint
- Multi-locale ApostropheCMS deployments with low-privilege authenticated users
Discovery Timeline
- 2026-10-20 - CVE-2026-113660 published to the National Vulnerability Database (NVD)
- 2026-10-20 - Last updated in NVD database
Technical Details for CVE-2026-113660
Vulnerability Analysis
The vulnerability resides in the ApostropheCMS exist-in-locale API. The endpoint is intended to check whether a document exists in a particular locale and mode. Instead of applying the standard document-level authorization criteria used elsewhere in the platform, it returns localized document identifiers to any authenticated caller.
An authenticated low-privilege user can therefore enumerate restricted documents across locales and modes, including unpublished draft content. The result is an information disclosure condition. Attackers do not gain the ability to read document bodies or modify data through this endpoint, but they can confirm the presence of specific documents, infer editorial workflow state, and map internal content structure.
The fix in version 4.33.0 adds the missing document-level view and edit authorization checks to the endpoint, aligning its behavior with the rest of the ApostropheCMS access control model.
Root Cause
The root cause is a missing authorization check [CWE-862]. The exist-in-locale handler returned localized document identifiers without validating whether the requesting user had view or edit permissions on the targeted documents. Authentication alone was treated as sufficient, bypassing the per-document authorization layer applied by other APIs.
Attack Vector
The attack vector is network-based and requires an authenticated session with low privileges. An attacker issues crafted requests to the exist-in-locale endpoint, iterating over document identifiers, locales, and modes such as draft. The endpoint responds with localized identifiers for documents that exist, allowing the attacker to confirm restricted content across the site.
// Security patch excerpt from ApostropheCMS 4.33.0
// packages/ai-helper/modules/@apostrophecms/ai-helper-image/index.js
methods(self) {
return {
scheduleCleanup() {
- setInterval(self.cleanup, 1000 * 60 * 60);
+ self.cleanupInterval = setInterval(self.cleanup, 1000 * 60 * 60);
},
async cleanup() {
Source: ApostropheCMS Commit f84fd41c
Detect Identity Attacks the Moment Authentication Fails
Singularity™ Identity surfaces credential misuse, lateral movement, and privilege escalation in real time, so you can contain the breach before it spreads.
Stop Identity AttacksDetection Methods for CVE-2026-113660
Indicators of Compromise
- Repeated authenticated requests from a single low-privilege account to the exist-in-locale API endpoint.
- Request patterns iterating over document identifiers, locale codes, or mode=draft parameters.
- Elevated response volumes from the exist-in-locale endpoint compared to historical baselines.
Detection Strategies
- Enable application-level request logging on all ApostropheCMS API routes, with particular attention to the exist-in-locale handler.
- Alert on authenticated sessions that issue high-rate enumeration queries against localization endpoints.
- Correlate low-privilege account activity with access attempts targeting draft-mode content identifiers.
Monitoring Recommendations
- Monitor web server and reverse proxy logs for bursts of exist-in-locale requests tied to the same session or token.
- Track the ApostropheCMS version in use across environments and flag any deployment running a version earlier than 4.33.0.
- Review audit trails for low-privilege accounts querying locales or modes outside their normal editorial scope.
How to Mitigate CVE-2026-113660
Immediate Actions Required
- Upgrade ApostropheCMS to version 4.33.0 or later across all environments.
- Review existing low-privilege accounts and revoke any that are unused or over-provisioned.
- Audit recent access logs for suspicious exist-in-locale query patterns prior to patching.
Patch Information
The vulnerability is fixed in ApostropheCMS 4.33.0. Review the ApostropheCMS Release 4.33.0 notes, the ApostropheCMS Security Advisory GHSA-vmxh-77cw-65j7, and the fix commits 9500b8b and f84fd41c for implementation details.
Workarounds
- Restrict access to the ApostropheCMS admin and API surface using network controls or an authenticating reverse proxy until the upgrade is complete.
- Temporarily disable or tightly limit low-privilege authenticated roles that do not require access to localized content APIs.
- Apply web application firewall rules to rate-limit or block requests targeting the exist-in-locale endpoint from non-trusted sources.
# Example npm upgrade command for ApostropheCMS
npm install apostrophe@4.33.0
npm ls 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

