https://db.gcve.eu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Wed, 21 Oct 2026 19:24:40 +0000 https://db.gcve.eu/vuln/fkie_cve-2026-113649 <p>ApostropheCMS is an open-source Node.js content management system. Prior to 3.7.1 of the import-export module and 4.34.0 of core ApostropheCMS, an editor who can import an enabled content type but lacks its stronger publication role can cause import write helpers to create, replace, or remove published variants without the normal publish permission and lifecycle checks. This issue is fixed in import-export 3.7.1 and ApostropheCMS 4.34.0.</p> <p>ApostropheCMS is an open-source Node.js content management system. Prior to 3.7.1 of the import-export module and 4.34.0 of core ApostropheCMS, an editor who can import an enabled content type but lacks its stronger publication role can cause import write helpers to create, replace, or remove published variants without the normal publish permission and lifecycle checks. This issue is fixed in import-export 3.7.1 and ApostropheCMS 4.34.0.</p> https://db.gcve.eu/vuln/fkie_cve-2026-113649 https://db.gcve.eu/vuln/ghsa-5m22-7pfq-vp65 <p><strong>Affected:</strong> npm: @apostrophecms/import-export, npm: apostrophe</p> <p>## Review scope and evidence limits</p> <p>Package: @apostrophecms/import-export, version 3.7.0.</p> <p>Release tag reviewed: @apostrophecms/import-export@3.7.0, commit 9500b8b0e1d630d5e07fbb5fd2c25ed0943845ce (September 30, 2026).</p> <p>Current main reviewed: 5ce3732be0ebdebb4db0f8ef160c81e8671157e6.</p> <p>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.</p> <p>## Import API bypasses publication roles for protected content</p> <p>The import gate in canImportOrExport() checks the type&#39;s import configuration and view permission. The write helpers then call document-manager insert/update directly, including operations on published variants. We did not find the normal publish permission check or beforePublish transition in these helpers. Core permissions intentionally distinguish editRole and publishRole, and the ordinary publication lifecycle enforces that distinction.</p> <p>The reported security boundary is a content type that an editor may edit but whose publication is reserved for a stronger role. Direc…</p> <p><strong>Affected:</strong> npm: @apostrophecms/import-export, npm: apostrophe</p> <p>## Review scope and evidence limits</p> <p>Package: @apostrophecms/import-export, version 3.7.0.</p> <p>Release tag reviewed: @apostrophecms/import-export@3.7.0, commit 9500b8b0e1d630d5e07fbb5fd2c25ed0943845ce (September 30, 2026).</p> <p>Current main reviewed: 5ce3732be0ebdebb4db0f8ef160c81e8671157e6.</p> <p>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.</p> <p>## Import API bypasses publication roles for protected content</p> <p>The import gate in canImportOrExport() checks the type&#39;s import configuration and view permission. The write helpers then call document-manager insert/update directly, including operations on published variants. We did not find the normal publish permission check or beforePublish transition in these helpers. Core permissions intentionally distinguish editRole and publishRole, and the ordinary publication lifecycle enforces that distinction.</p> <p>The reported security boundary is a content type that an editor may edit but whose publication is reserved for a stronger role. Direc…</p> https://db.gcve.eu/vuln/ghsa-5m22-7pfq-vp65