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-112954 Overview
CVE-2026-112954 is an information disclosure vulnerability in ApostropheCMS, an open-source Node.js content management system. The flaw affects public REST API types that use publicApiProjection to restrict returned fields. Prior to version 4.34.0, excluded searchable and sortable fields can still be inferred through search membership and sort ordering oracles. Returned responses continue to honor the projection, so attackers cannot dump hidden fields directly. Instead, they can issue targeted queries that reveal information about excluded values based on which documents match or how results are ordered. The issue is tracked under [CWE-200] (Exposure of Sensitive Information to an Unauthorized Actor) and is fixed in version 4.34.0.
Critical Impact
Unauthenticated network attackers can infer values of fields that administrators intended to hide from the public REST API, undermining the confidentiality contract of publicApiProjection.
Affected Products
- ApostropheCMS versions prior to 4.34.0
- Deployments exposing public REST API types configured with publicApiProjection
- Node.js applications built on the apostrophe npm package
Discovery Timeline
- 2026-10-20 - CVE-2026-112954 published to the National Vulnerability Database
- 2026-10-20 - Last updated in NVD database
Technical Details for CVE-2026-112954
Vulnerability Analysis
ApostropheCMS exposes document types through a public REST API. Developers use the publicApiProjection option to restrict which fields are returned to unauthenticated callers. The projection correctly filters response payloads, but the underlying query layer still allows search and sort operations to reference excluded fields. This mismatch creates inference oracles rather than an unrestricted field dump.
An attacker queries the API using the full-text search parameter or by requesting a sort on an excluded field. The service answers whether a document matches the search term and in what order documents appear. By iterating over candidate values, the attacker reconstructs excluded field contents one bit, character, or ordering position at a time.
Because the API is unauthenticated and reachable over the network, exploitation requires only HTTP access to the target site. The confidentiality impact is limited to fields that were deliberately excluded from publicApiProjection, which is why the base score is scoped to low confidentiality impact with no integrity or availability effect.
Root Cause
The root cause is incomplete enforcement of the projection boundary. publicApiProjection was treated as a response-shaping filter rather than as an authorization boundary spanning search indexes and sort keys. Query parameters that reference excluded fields were still honored by the backing data layer, producing observable differences in results.
Attack Vector
An unauthenticated attacker crafts REST requests against a public API-enabled document type. By varying search, sort, and filter parameters that target excluded fields, the attacker observes whether documents appear in results and in what order. The side-channel signals permit reconstruction of hidden values without ever receiving them in the response body.
The fix in version 4.34.0 extends projection enforcement into related query paths. Related commits also tighten adjacent server-side handling, including removal of forbidden fields in area rendering.
// From ApostropheCMS commit 40b989b — packages/apostrophe/modules/@apostrophecms/area/index.js
// its normal properties. Otherwise a rendering of the entire area
// is supplied as the `_rendered` property of that area and the
// `items` array is suppressed from the response.
//
// 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. The patch introduces removeForbiddenFieldsDeep before area rendering, ensuring fields the caller may not view are stripped before downstream processing.
Detection Methods for CVE-2026-112954
Indicators of Compromise
- Repeated unauthenticated REST API requests that iterate search values against the same document type endpoint.
- Sequences of requests that only vary a sort parameter targeting fields not included in the public response payload.
- High-volume enumeration patterns from a single source IP against public ApostropheCMS endpoints.
Detection Strategies
- Review web server and application logs for query strings referencing field names that are not expected in public responses.
- Compare query parameters against the configured publicApiProjection for each piece or page type and alert on mismatches.
- Baseline normal public API traffic volume per document type and flag abrupt spikes in search or sort parameter variation.
Monitoring Recommendations
- Enable verbose logging on the ApostropheCMS REST API tier to capture full query parameters, source IP, and timing.
- Forward web and application logs to a centralized analytics platform for correlation and anomaly detection.
- Alert on sustained enumeration behavior, such as hundreds of similar REST calls differing only in a single parameter value.
How to Mitigate CVE-2026-112954
Immediate Actions Required
- Upgrade the apostrophe package to version 4.34.0 or later across all environments.
- Audit every piece and page type for use of publicApiProjection and confirm that excluded fields are actually sensitive.
- Rate-limit unauthenticated REST API endpoints to reduce the feasibility of iterative inference.
Patch Information
ApostropheCMS version 4.34.0 contains the fix. See the ApostropheCMS Release 4.34.0 notes and the GitHub Security Advisory GHSA-rqgm-cfrp-4hx8. Relevant source changes are in ApostropheCMS Commit 06e4b37 and ApostropheCMS Commit 40b989b.
Workarounds
- Disable the public REST API for document types that contain sensitive fields until the upgrade is deployed.
- Store highly sensitive values in separate document types that are not published through any public API.
- Place a web application firewall rule in front of the API to block search and sort parameters that reference non-public field names.
# Upgrade ApostropheCMS to the patched release
npm install apostrophe@4.34.0 --save
# Verify the installed version
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

