Live › vulnerability › CVE-2026-112956
Go to dashboardThe archive duplicate-continuation step in @apostrophecms/import-export accepts client-supplied replacement choices instead of binding them to the user's own duplicate analysis, so it does not reliably check publication authority before updating a target. An attacker with contributor (draft-editing) rights can use it to overwrite published content on an import-enabled localized content type.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 19:11 UTC, 3h before NVD. All times on this page are UTC.
| Product | Ecosystem | Affected | Fixed in |
|---|---|---|---|
| @apostrophecms/import-export | npm | < 3.7.1 | 3.7.1 |
npm ls @apostrophecms/import-export anything below 3.7.1 is affected3.7.1 or laterEach row is the first time that source carried this signal. The analyst’s rows are its own findings.
Package: @apostrophecms/import-export, version 3.7.0.
Release tag reviewed: @apostrophecms/[email protected], commit 9500b8b0e1d630d5e07fbb5fd2c25ed0943845ce (September 30, 2026).
Current main reviewed: 5ce3732be0ebdebb4db0f8ef160c81e8671157e6.
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.
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.
The original report describes a contributor crossing the publication boundary through duplicate replacement on an import-enabled localized type. We have not repeated that end-to-end sequence on 3.7.0.
Suggested remediation: bind continuation state to the initiating user, archive, job, permitted source/target mapping, locale and mode; reject inconsistent identity metadata; derive permissions from the actual loaded target and require publication authority for published targets.
Source: overrideDuplicates(), replaceDocId(), and insertOrUpdateDoc() in the importer.
Vivek R / Winfunc Original reporting team: Mufeed VH / Winfunc
This page as .md · .json · in your agent: get_signal("CVE-2026-112956")
GitHub Advisory Database, CC-BY 4.0 · NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.