ApostropheCMS: Archive duplicate continuation lets contributors overwrite published content
Review scope and evidence limits
Package: @apostrophecms/import-export, version 3.7.0.
Release tag reviewed: @apostrophecms/import-export@3.7.0, 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 branch. This follow-up is a static remediation review. The original end-to-end reproductions have not been repeated against the latest release or tested on 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 code. The original emailed PDF contains the original reproduction material; refer to that existing private attachment.
Archive duplicate continuation permits unauthorized published-content replacement
The overrideDuplicates() continuation 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 the source level.
The original report describes a contributor crossing the publication boundary through duplicate replacement on an import-enabled localized type. That end-to-end sequence has not been repeated 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.).
Coordination
- Vivek R / Winfunc
- Original reporting team: Mufeed VH / Winfunc
What to do
Upgrade @apostrophecms/import-export to version 3.7.1 or higher.
Suggested architectural remediation from the report: 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.
Affected software
Click a technology to see all vulnerabilities affecting it.
| Platform | Package | Vulnerable versions | Fixed in |
|---|---|---|---|
| npm package | @apostrophecms/import-export | < 3.7.1 | 3.7.1 |
References
- https://github.com/apostrophecms/apostrophe/security/advisories/GHSA-jf5h-36mg-rp6x
- https://nvd.nist.gov/vuln/detail/CVE-2026-112956
- https://github.com/apostrophecms/apostrophe/commit/06e4b377f3c360f9e89c32dccd7e505ad5ddf498
- https://github.com/apostrophecms/apostrophe/commit/40b989b1a9dd23d30029b8ce7668634265cfe5ea
- https://github.com/apostrophecms/apostrophe
- https://github.com/apostrophecms/apostrophe/releases/tag/@apostrophecms/import-export@3.7.1
- CVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N- Weakness (CWE)
CWE-863- Platform
- npm
- Package
@apostrophecms/import-export- Disclosed
- 21.10.2026
- Updated
- 21.10.2026 20:17
Sources and licenses · Edited or translated by DockRay; source rights and applicable licenses are retained.
OSV / GitHub Advisory Database - GHSA-jf5h-36mg-rp6x - CC BY 4.0
Vulnerability history: @apostrophecms/import-export
All published vulnerabilities of this package (npm package), newest first. Shows whether this is a one-off slip or a package that needs watching.
- Total entries
- 9
- First → latest
- 03.2026 10.2026
- Without a fix
- 0
- Exploited in attacks
- 0
Severity breakdown
- Critical 1
- High 1
- Medium 6
- Low 1
Disclosures per year
- 2026: 9
-
ApostropheCMS: Archive duplicate continuation lets contributors overwrite published content this entry
Know which vulnerabilities affect your application
With the DockRay integration and software inventory enabled, DockRay checks reported component versions against known vulnerabilities and notifies you about confirmed matches. Coverage depends on the supported technology and available advisory data.