<?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 16:59:27 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-112956</title>
      <link>https://db.gcve.eu/vuln/fkie_cve-2026-112956</link>
      <description>&lt;p&gt;ApostropheCMS is an open-source Node.js content management system. Prior to 3.7.1 of the import-export module, duplicate-import continuation accepts client-controlled replacement choices without binding them to a user-owned server-side analysis or authorizing the canonical target. On an import-enabled localized type, a contributor with draft editing authority can cross the publication boundary by selecting a published document for replacement, although the current assessment is based on remediation review rather than a repeated end-to-end reproduction. This issue is fixed in version 3.7.1.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;ApostropheCMS is an open-source Node.js content management system. Prior to 3.7.1 of the import-export module, duplicate-import continuation accepts client-controlled replacement choices without binding them to a user-owned server-side analysis or authorizing the canonical target. On an import-enabled localized type, a contributor with draft editing authority can cross the publication boundary by selecting a published document for replacement, although the current assessment is based on remediation review rather than a repeated end-to-end reproduction. This issue is fixed in version 3.7.1.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/fkie_cve-2026-112956</guid>
    </item>
    <item>
      <title>GHSA-jf5h-36mg-rp6x — ApostropheCMS: Archive duplicate continuation lets contributors overwrite published content</title>
      <link>https://db.gcve.eu/vuln/ghsa-jf5h-36mg-rp6x</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: @apostrophecms/import-export&lt;/p&gt;
&lt;p&gt;## Review scope and evidence limits&lt;/p&gt;
&lt;p&gt;Package: @apostrophecms/import-export, version 3.7.0.&lt;/p&gt;
&lt;p&gt;Release tag reviewed: @apostrophecms/import-export@3.7.0, commit 9500b8b0e1d630d5e07fbb5fd2c25ed0943845ce (September 30, 2026).&lt;/p&gt;
&lt;p&gt;Current main reviewed: 5ce3732be0ebdebb4db0f8ef160c81e8671157e6.&lt;/p&gt;
&lt;p&gt;The importer, gzip extractor, import permission gate, and core permission implementation have no differences between that release tag and the reviewed main. This follow-up is a static remediation review. We have not repeated the original end-to-end reproductions against the latest release or tested a deployed site. Current exploitability and impact therefore still require maintainer validation; the observations below establish that the reported security checks remain absent in public source. The original emailed PDF contains the original reproduction material. Please refer to that existing private attachment.&lt;/p&gt;
&lt;p&gt;## Archive duplicate continuation permits unauthorized published-content replacement&lt;/p&gt;
&lt;p&gt;The overrideDuplicates() continuation still accepts client-supplied replacement choices, rather than binding them to a server-maintained, user-owned duplicate analysis. The replacement and write helpers do not establish a single canonical resource identity and authorization context before the update. This leaves the reported gap between draft editing authority and the published target selected for replacement unresolved at source level.&lt;/p&gt;
&lt;p&gt;The original report describes a contributor crossing the publicati…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: @apostrophecms/import-export&lt;/p&gt;
&lt;p&gt;## Review scope and evidence limits&lt;/p&gt;
&lt;p&gt;Package: @apostrophecms/import-export, version 3.7.0.&lt;/p&gt;
&lt;p&gt;Release tag reviewed: @apostrophecms/import-export@3.7.0, commit 9500b8b0e1d630d5e07fbb5fd2c25ed0943845ce (September 30, 2026).&lt;/p&gt;
&lt;p&gt;Current main reviewed: 5ce3732be0ebdebb4db0f8ef160c81e8671157e6.&lt;/p&gt;
&lt;p&gt;The importer, gzip extractor, import permission gate, and core permission implementation have no differences between that release tag and the reviewed main. This follow-up is a static remediation review. We have not repeated the original end-to-end reproductions against the latest release or tested a deployed site. Current exploitability and impact therefore still require maintainer validation; the observations below establish that the reported security checks remain absent in public source. The original emailed PDF contains the original reproduction material. Please refer to that existing private attachment.&lt;/p&gt;
&lt;p&gt;## Archive duplicate continuation permits unauthorized published-content replacement&lt;/p&gt;
&lt;p&gt;The overrideDuplicates() continuation still accepts client-supplied replacement choices, rather than binding them to a server-maintained, user-owned duplicate analysis. The replacement and write helpers do not establish a single canonical resource identity and authorization context before the update. This leaves the reported gap between draft editing authority and the published target selected for replacement unresolved at source level.&lt;/p&gt;
&lt;p&gt;The original report describes a contributor crossing the publicati…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ghsa-jf5h-36mg-rp6x</guid>
    </item>
  </channel>
</rss>
