<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://db.gcve.eu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-22T22:02:48.333333+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@gcve.eu</email>
  </author>
  <link href="https://db.gcve.eu" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://db.gcve.eu/vuln/fkie_cve-2026-113668</id>
    <title>fkie_cve-2026-113668</title>
    <updated>2026-10-22T22:02:48.356433+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>ApostropheCMS is an open-source Node.js content management system. Prior to 4.33.0, the REST route GET /api/v1/&lt;piece-type&gt;/:_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. This issue is fixed in version 4.33.0.</p>
      </div>
    </content>
    <link href="https://db.gcve.eu/vuln/fkie_cve-2026-113668"/>
  </entry>
  <entry>
    <id>https://db.gcve.eu/vuln/ghsa-gqh3-7856-rjjg</id>
    <title>GHSA-gqh3-7856-rjjg — ApostropheCMS: :_id/locales REST route omits the public-API authorization gate its sibling read routes enforce (unauthe…</title>
    <updated>2026-10-22T22:02:48.356745+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> npm: apostrophe</p>
<p>## Summary
The REST route `GET /api/v1/&lt;piece-type&gt;/:_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 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/&lt;piece-type&gt;/:_id/locales` and `GET /api/v1/@apostrophecms/page/:_id/locales`.</p>
<p>## 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's locale/publication metadata without authorization.</p>
<p>## Impact</p>
<p>An unauthenticated caller can confirm t…</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/ghsa-gqh3-7856-rjjg"/>
  </entry>
</feed>
