GHSA-GQH3-7856-RJJG
Vulnerability from github – Published: 2026-10-20 18:14 – Updated: 2026-10-20 18:14Summary
The REST route GET /api/v1/<piece-type>/:_id/locales (and the equivalent page route) does not apply the publicApiCheckAsync gate that ApostropheCMS's other read routes enforce. An unauthenticated caller can therefore query this route for any document _id and learn whether the document exists and which locales it is published in — a document-existence and locale-metadata disclosure that the read-API is otherwise supposed to gate.
Affected
- Repository:
apostrophecms/apostrophe(monorepo packageapostrophe). - Confirmed at 4.32.2 (commit
d3ff8c9== the shipped 4.32.2; unchanged at current HEAD). No fix at time of report. - Stack: Node.js / Express + MongoDB.
- Endpoints:
GET /api/v1/<piece-type>/:_id/localesandGET /api/v1/@apostrophecms/page/:_id/locales.
Technical detail
- Unsafe:
modules/@apostrophecms/piece-type/index.js:397registers the:_id/localesroute with nopublicApiCheckAsync. The page module has the same omission atmodules/@apostrophecms/page/index.js:925. - Gated siblings: the read routes in the same module (e.g.
getAllatpiece-type/index.js:256-263) callpublicApiCheckAsync(:263) to enforce the public-API access policy. - So the
localeshandler (which callsgetLocales()for the document) runs for any caller regardless of the public-API gate the other read routes apply, returning the document's locale/publication metadata without authorization.
Impact
An unauthenticated caller can confirm the existence of a document by _id and enumerate its locales/publication state — information the read-API is meant to gate. Defensibly 4.3 (AC:H) given the opaque _id precondition (the caller needs a document id).
How it was verified (local only)
Reproduced against apostrophe@4.32.2 (== commit d3ff8c9) locally with synthetic content:
- Source review confirmed the :_id/locales route lacks publicApiCheckAsync while the sibling read routes have it.
- An unauthenticated GET /api/v1/<piece-type>/<_id>/locales returned the document's locale metadata (existence + locales), while the gated read routes (e.g. getAll) correctly required the public-API policy.
- Control: the same route with the publicApiCheckAsync gate added (matching the siblings) denies the unauthenticated request — isolating the missing gate as the cause.
Synthetic content only; nothing hosted was touched.
Remediation
Add the publicApiCheckAsync (or equivalent) authorization gate to the :_id/locales route in both the piece-type and page modules, matching the sibling read routes, so the locale/existence metadata is only returned to callers permitted by the public-API policy.
Credit
Please credit Santosh Kumar Puppala (https://github.com/Santoshkumarpuppala).
{
"affected": [
{
"package": {
"ecosystem": "npm",
"name": "apostrophe"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "4.33.0"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2026-113668"
],
"database_specific": {
"cwe_ids": [
"CWE-200",
"CWE-862"
],
"github_reviewed": true,
"github_reviewed_at": "2026-10-20T18:14:32Z",
"nvd_published_at": null,
"severity": "MODERATE"
},
"details": "## Summary\nThe REST route `GET /api/v1/\u003cpiece-type\u003e/:_id/locales` (and the equivalent page route) does not apply the `publicApiCheckAsync` gate that ApostropheCMS\u0027s other read routes enforce. An unauthenticated caller can therefore query this route for any document `_id` and learn whether the document exists and which locales it is published in \u2014 a document-existence and locale-metadata disclosure that the read-API is otherwise supposed to gate.\n \n## Affected\n- Repository: `apostrophecms/apostrophe` (monorepo package `apostrophe`).\n- Confirmed at **4.32.2** (commit `d3ff8c9` == the shipped 4.32.2; unchanged at current HEAD). No fix at time of report.\n- Stack: Node.js / Express + MongoDB.\n- Endpoints: `GET /api/v1/\u003cpiece-type\u003e/:_id/locales` and `GET /api/v1/@apostrophecms/page/:_id/locales`.\n\n## Technical detail\n- Unsafe: `modules/@apostrophecms/piece-type/index.js:397` registers the `:_id/locales` route with **no** `publicApiCheckAsync`. The page module has the same omission at `modules/@apostrophecms/page/index.js:925`.\n- Gated siblings: the read routes in the same module (e.g. `getAll` at `piece-type/index.js:256-263`) call `publicApiCheckAsync` (`:263`) to enforce the public-API access policy.\n- So the `locales` handler (which calls `getLocales()` for the document) runs for any caller regardless of the public-API gate the other read routes apply, returning the document\u0027s locale/publication metadata without authorization.\n\n## Impact\n\nAn unauthenticated caller can confirm the existence of a document by `_id` and enumerate its locales/publication state \u2014 information the read-API is meant to gate. Defensibly 4.3 (AC:H) given the opaque `_id` precondition (the caller needs a document id).\n \n## How it was verified (local only)\nReproduced against `apostrophe@4.32.2` (== commit `d3ff8c9`) locally with synthetic content:\n- Source review confirmed the `:_id/locales` route lacks `publicApiCheckAsync` while the sibling read routes have it.\n- An **unauthenticated** `GET /api/v1/\u003cpiece-type\u003e/\u003c_id\u003e/locales` returned the document\u0027s locale metadata (existence + locales), while the gated read routes (e.g. `getAll`) correctly required the public-API policy.\n- Control: the same route with the `publicApiCheckAsync` gate added (matching the siblings) denies the unauthenticated request \u2014 isolating the missing gate as the cause.\nSynthetic content only; nothing hosted was touched.\n \n## Remediation\nAdd the `publicApiCheckAsync` (or equivalent) authorization gate to the `:_id/locales` route in both the piece-type and page modules, matching the sibling read routes, so the locale/existence metadata is only returned to callers permitted by the public-API policy.\n \n## Credit\nPlease credit **Santosh Kumar Puppala** (https://github.com/Santoshkumarpuppala).",
"id": "GHSA-gqh3-7856-rjjg",
"modified": "2026-10-20T18:14:33Z",
"published": "2026-10-20T18:14:32Z",
"references": [
{
"type": "WEB",
"url": "https://github.com/apostrophecms/apostrophe/security/advisories/GHSA-gqh3-7856-rjjg"
},
{
"type": "WEB",
"url": "https://github.com/apostrophecms/apostrophe/commit/9500b8b0e1d630d5e07fbb5fd2c25ed0943845ce"
},
{
"type": "WEB",
"url": "https://github.com/apostrophecms/apostrophe/commit/f84fd41cbf6c22eb8d0008fc9c25df1f7130b350"
},
{
"type": "PACKAGE",
"url": "https://github.com/apostrophecms/apostrophe"
},
{
"type": "WEB",
"url": "https://github.com/apostrophecms/apostrophe/releases/tag/apostrophe@4.33.0"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N",
"type": "CVSS_V3"
}
],
"summary": "ApostropheCMS: :_id/locales REST route omits the public-API authorization gate its sibling read routes enforce (unauthenticated doc-existence + locale metadata disclosure)"
}
Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline
Sightings and recorded dates, grouped by day · UTC
Loading timeline…
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.