Skip to content
Heist/ feed
Back to feed
MediumFix available

ApostropheCMS: Authenticated Object-Level Authorization Bypass in exist-in-locale Reveals Restricted Localized Draft Identifiers

Type: advisorySources: OSV

**Summary** ApostropheCMS’s exist-in-locale API allows an authenticated low-privilege user to determine whether restricted documents exist in a specified locale and mode, including draft mode. The endpoint returns localized document identifiers without applying document-level view or edit authorization criteria. The issue was reproduced against a real local ApostropheCMS application running the reviewed source code. The test used a synthetic guest account and synthetic restricted draft records. **Details** Exact vulnerable source path: ` packages/apostrophe/modules/@apostrophecms/i18n/index.js:503-529` Exact API route:` POST /api/v1/@apostrophecms/i18n/exist-in-locale` The handler verifies only that the requester is authenticated: ``` if (!req.user) { throw self.apos.error('notfound'); } ``` It then performs a direct database lookup using attacker-controlled document IDs, locale, and mode: ``` const found = await self.apos.doc.db.find({ aposLocale: `${locale}:${mode}`, aposDocId: { $in: ids.map(self.apos.doc.toAposDocId) } }).project({ _id: 1, aposDocId: 1 }).toArray(); ``` This query does not apply: .permission('view') .permission('edit') apos.permission.criteria(req, 'view') object-level document authorization locale-specific authorization The endpoint accepts multiple IDs, making bulk probing possible. **Proof of Concept** The local application was running at: http://127.0.0.1:3000 The test account had the low-privilege role: guest The local database contained synthetic re

Products
apostrophe
Affected versions
Not specified
Fixed versions
4.33.0
CVEs
CVE-2026-113660
Confirmed fixed CVEs
Not specified
Updated in this feed
31 Oct 2026, 13:14 UTC · Revision 1

Source evidence

ApostropheCMS: Authenticated Object-Level Authorization Bypass in exist-in-locale Reveals Restricted Localized Draft Identifiers

core-osv · Original source

Published 20 Oct 2026, 18:19 UTC

**Summary** ApostropheCMS’s exist-in-locale API allows an authenticated low-privilege user to determine whether restricted documents exist in a specified locale and mode, including draft mode. The endpoint returns localized document identifiers without applying document-level view or edit authorization criteria. The issue was reproduced against a real local ApostropheCMS application running the reviewed source code. The test used a synthetic guest account and synthetic restricted draft records. **Details** Exact vulnerable source path: ` packages/apostrophe/modules/@apostrophecms/i18n/index.js:503-529` Exact API route:` POST /api/v1/@apostrophecms/i18n/exist-in-locale` The handler verifies only that the requester is authenticated: ``` if (!req.user) { throw self.apos.error('notfound'); } ``` It then performs a direct database lookup using attacker-controlled document IDs, locale, and mode: ``` const found = await self.apos.doc.db.find({ aposLocale: `${locale}:${mode}`, aposDocId: { $in: ids.map(self.apos.doc.toAposDocId) } }).project({ _id: 1, aposDocId: 1 }).toArray(); ``` This query does not apply: .permission('view') .permission('edit') apos.permission.criteria(req, 'view') object-level document authorization locale-specific authorization The endpoint accepts multiple IDs, making bulk probing possible. **Proof of Concept** The local application was running at: http://127.0.0.1:3000 The test account had the low-privilege role: guest The local database contained synthetic re

osv:GHSA-vmxh-77cw-65j7

apostrophe

Fixed versions: 4.33.0

Complete source record
{
  "id": "cad85c78d73bebc21dbc6d8ba120f0c7da5994953618db8600aef16db8e50045",
  "url": "https://osv.dev/vulnerability/GHSA-vmxh-77cw-65j7",
  "method": "structured",
  "payload": {
    "kind": "advisory",
    "title": "ApostropheCMS: Authenticated Object-Level Authorization Bypass in exist-in-locale Reveals Restricted Localized Draft Identifiers",
    "summary": "**Summary** ApostropheCMS’s exist-in-locale API allows an authenticated low-privilege user to determine whether restricted documents exist in a specified locale and mode, including draft mode. The endpoint returns localized document identifiers without applying document-level view or edit authorization criteria. The issue was reproduced against a real local ApostropheCMS application running the reviewed source code. The test used a synthetic guest account and synthetic restricted draft records. **Details** Exact vulnerable source path: ` packages/apostrophe/modules/@apostrophecms/i18n/index.js:503-529` Exact API route:` POST /api/v1/@apostrophecms/i18n/exist-in-locale` The handler verifies only that the requester is authenticated: ``` if (!req.user) { throw self.apos.error('notfound'); } ``` It then performs a direct database lookup using attacker-controlled document IDs, locale, and mode: ``` const found = await self.apos.doc.db.find({ aposLocale: `${locale}:${mode}`, aposDocId: { $in: ids.map(self.apos.doc.toAposDocId) } }).project({ _id: 1, aposDocId: 1 }).toArray(); ``` This query does not apply: .permission('view') .permission('edit') apos.permission.criteria(req, 'view') object-level document authorization locale-specific authorization The endpoint accepts multiple IDs, making bulk probing possible. **Proof of Concept** The local application was running at: http://127.0.0.1:3000 The test account had the low-privilege role: guest The local database contained synthetic re",
    "evidence": "osv:GHSA-vmxh-77cw-65j7",
    "products": [
      {
        "name": {
          "value": "apostrophe",
          "evidence": "/affected/0/package/name"
        },
        "prerequisites": [],
        "fixed_versions": [
          {
            "value": "4.33.0",
            "evidence": "/affected/0/ranges"
          }
        ],
        "affected_versions": []
      }
    ],
    "severity": "medium",
    "structured": {
      "id": "GHSA-vmxh-77cw-65j7",
      "aliases": [
        "CVE-2026-113660",
        "GHSA-vmxh-77cw-65j7"
      ],
      "metrics": [
        {
          "type": "CVSS_V3",
          "score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N"
        }
      ],
      "affected": [
        {
          "ranges": [
            {
              "type": "SEMVER",
              "events": [
                {
                  "introduced": "0"
                },
                {
                  "fixed": "4.33.0"
                }
              ]
            }
          ],
          "package": {
            "name": "apostrophe",
            "purl": "pkg:npm/apostrophe",
            "ecosystem": "npm"
          },
          "database_specific": {
            "source": "https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2026/10/GHSA-vmxh-77cw-65j7/GHSA-vmxh-77cw-65j7.json"
          }
        }
      ],
      "modified": "2026-10-20T18:30:03.592369183Z",
      "provider": "osv",
      "references": [
        "https://github.com/apostrophecms/apostrophe/security/advisories/GHSA-vmxh-77cw-65j7",
        "https://github.com/apostrophecms/apostrophe/commit/9500b8b0e1d630d5e07fbb5fd2c25ed0943845ce",
        "https://github.com/apostrophecms/apostrophe/commit/f84fd41cbf6c22eb8d0008fc9c25df1f7130b350",
        "https://github.com/apostrophecms/apostrophe",
        "https://github.com/apostrophecms/apostrophe/releases/tag/apostrophe@4.33.0"
      ],
      "provider_metadata": {
        "cwe_ids": [
          "CWE-862"
        ],
        "severity": "MODERATE",
        "github_reviewed": true,
        "nvd_published_at": null,
        "github_reviewed_at": "2026-10-20T18:19:34Z"
      }
    },
    "related_cves": [
      {
        "value": "CVE-2026-113660",
        "evidence": "/aliases"
      }
    ],
    "security_relevant": true,
    "severity_evidence": "/severity/0/score"
  },
  "source_id": "core-osv",
  "document_id": 390149,
  "published_at": "2026-10-20T18:19:34+00:00"
}