<?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 22:02:49 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-113668</title>
      <link>https://db.gcve.eu/vuln/fkie_cve-2026-113668</link>
      <description>&lt;p&gt;ApostropheCMS is an open-source Node.js content management system. Prior to 4.33.0, the REST route GET /api/v1/&amp;lt;piece-type&amp;gt;/:_id/locales (and the equivalent page route) does not apply the publicApiCheckAsync gate that ApostropheCMS&amp;#39;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. This issue is fixed in version 4.33.0.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;ApostropheCMS is an open-source Node.js content management system. Prior to 4.33.0, the REST route GET /api/v1/&amp;lt;piece-type&amp;gt;/:_id/locales (and the equivalent page route) does not apply the publicApiCheckAsync gate that ApostropheCMS&amp;#39;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. This issue is fixed in version 4.33.0.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/fkie_cve-2026-113668</guid>
    </item>
    <item>
      <title>GHSA-gqh3-7856-rjjg — ApostropheCMS: :_id/locales REST route omits the public-API authorization gate its sibling read routes enforce (unauthe…</title>
      <link>https://db.gcve.eu/vuln/ghsa-gqh3-7856-rjjg</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: apostrophe&lt;/p&gt;
&lt;p&gt;## Summary
The REST route `GET /api/v1/&amp;lt;piece-type&amp;gt;/:_id/locales` (and the equivalent page route) does not apply the `publicApiCheckAsync` gate that ApostropheCMS&amp;#39;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 package `apostrophe`).
- 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/&amp;lt;piece-type&amp;gt;/:_id/locales` and `GET /api/v1/@apostrophecms/page/:_id/locales`.&lt;/p&gt;
&lt;p&gt;## Technical detail
- 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`.
- 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.
- 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&amp;#39;s locale/publication metadata without authorization.&lt;/p&gt;
&lt;p&gt;## Impact&lt;/p&gt;
&lt;p&gt;An unauthenticated caller can confirm t…&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 REST route `GET /api/v1/&amp;lt;piece-type&amp;gt;/:_id/locales` (and the equivalent page route) does not apply the `publicApiCheckAsync` gate that ApostropheCMS&amp;#39;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 package `apostrophe`).
- 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/&amp;lt;piece-type&amp;gt;/:_id/locales` and `GET /api/v1/@apostrophecms/page/:_id/locales`.&lt;/p&gt;
&lt;p&gt;## Technical detail
- 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`.
- 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.
- 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&amp;#39;s locale/publication metadata without authorization.&lt;/p&gt;
&lt;p&gt;## Impact&lt;/p&gt;
&lt;p&gt;An unauthenticated caller can confirm t…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ghsa-gqh3-7856-rjjg</guid>
    </item>
  </channel>
</rss>
