<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://db.gcve.eu</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Thu, 22 Oct 2026 23:00:16 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-112957</title>
      <link>https://db.gcve.eu/vuln/fkie_cve-2026-112957</link>
      <description>&lt;p&gt;ApostropheCMS is an open-source Node.js content management system. Prior to 4.34.0, the getOne REST endpoint for pages does not apply viewRole type-level restrictions or viewPermission field-level redaction. An editor-level user who knows a document _id can read the full content of admin-only pages and their privileged fields, while the getAll endpoint correctly enforces both restrictions. This issue is fixed in version 4.34.0.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;ApostropheCMS is an open-source Node.js content management system. Prior to 4.34.0, the getOne REST endpoint for pages does not apply viewRole type-level restrictions or viewPermission field-level redaction. An editor-level user who knows a document _id can read the full content of admin-only pages and their privileged fields, while the getAll endpoint correctly enforces both restrictions. This issue is fixed in version 4.34.0.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/fkie_cve-2026-112957</guid>
    </item>
    <item>
      <title>GHSA-vh56-5m88-39rq — ApostropheCMS: GET /api/v1/@apostrophecms/page/:id bypasses viewRole restriction and exposes viewPermission-gated field…</title>
      <link>https://db.gcve.eu/vuln/ghsa-vh56-5m88-39rq</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: apostrophe&lt;/p&gt;
&lt;p&gt;### Summary
The `getOne` REST endpoint for pages does not apply `viewRole` type-level restrictions
or `viewPermission` field-level redaction. An editor-level user who knows a document
`_id` can read the full content of admin-only pages and their privileged fields, while
the `getAll` endpoint correctly enforces both restrictions.&lt;/p&gt;
&lt;p&gt;### Details
**Finding 3 — viewRole bypass:**
`modules/@apostrophecms/page/index.js` exposes `getRestQuery(req, omitPermissionCheck =
false)`. The `getAll` path calls `publicApiCheckAsync` and threads the full query builder
pipeline including `viewRole` filtering. The `getOne` path uses a divergent code path
that skips this pipeline.&lt;/p&gt;
&lt;p&gt;A page type declared with `viewRole: &amp;#39;admin&amp;#39;` is inaccessible via `GET
/api/v1/@apostrophecms/page?type=secretPage` (returns 403 to an editor) but is fully
returned by `GET /api/v1/@apostrophecms/page/:id:en:published` to the same editor.&lt;/p&gt;
&lt;p&gt;**Finding 4 — viewPermission field leak:**
Fields decorated with `viewPermission: { action: &amp;#39;edit&amp;#39;, type: &amp;#39;@apostrophecms/page&amp;#39; }`
are stripped by `removeForbiddenFields` in the `getAll` path but are returned verbatim
in `getOne`. An editor who knows any document `_id` can read all
`viewPermission`-restricted fields.&lt;/p&gt;
&lt;p&gt;### PoC
```bash
# Log in as editor, get session jar
EDITOR_JAR=&amp;#34;...&amp;#34;&lt;/p&gt;
&lt;p&gt;# getAll — correctly blocked
curl -b &amp;#34;$EDITOR_JAR&amp;#34; \
  &amp;#34;http://TARGET/api/v1/@apostrophecms/page?type=secretPage&amp;#34;
# → 403 Forbidden&lt;/p&gt;
&lt;p&gt;# getOne — bypassed, returns full document including viewPermission…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: apostrophe&lt;/p&gt;
&lt;p&gt;### Summary
The `getOne` REST endpoint for pages does not apply `viewRole` type-level restrictions
or `viewPermission` field-level redaction. An editor-level user who knows a document
`_id` can read the full content of admin-only pages and their privileged fields, while
the `getAll` endpoint correctly enforces both restrictions.&lt;/p&gt;
&lt;p&gt;### Details
**Finding 3 — viewRole bypass:**
`modules/@apostrophecms/page/index.js` exposes `getRestQuery(req, omitPermissionCheck =
false)`. The `getAll` path calls `publicApiCheckAsync` and threads the full query builder
pipeline including `viewRole` filtering. The `getOne` path uses a divergent code path
that skips this pipeline.&lt;/p&gt;
&lt;p&gt;A page type declared with `viewRole: &amp;#39;admin&amp;#39;` is inaccessible via `GET
/api/v1/@apostrophecms/page?type=secretPage` (returns 403 to an editor) but is fully
returned by `GET /api/v1/@apostrophecms/page/:id:en:published` to the same editor.&lt;/p&gt;
&lt;p&gt;**Finding 4 — viewPermission field leak:**
Fields decorated with `viewPermission: { action: &amp;#39;edit&amp;#39;, type: &amp;#39;@apostrophecms/page&amp;#39; }`
are stripped by `removeForbiddenFields` in the `getAll` path but are returned verbatim
in `getOne`. An editor who knows any document `_id` can read all
`viewPermission`-restricted fields.&lt;/p&gt;
&lt;p&gt;### PoC
```bash
# Log in as editor, get session jar
EDITOR_JAR=&amp;#34;...&amp;#34;&lt;/p&gt;
&lt;p&gt;# getAll — correctly blocked
curl -b &amp;#34;$EDITOR_JAR&amp;#34; \
  &amp;#34;http://TARGET/api/v1/@apostrophecms/page?type=secretPage&amp;#34;
# → 403 Forbidden&lt;/p&gt;
&lt;p&gt;# getOne — bypassed, returns full document including viewPermission…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ghsa-vh56-5m88-39rq</guid>
    </item>
  </channel>
</rss>
