ApostropheCMS: Archive duplicate continuation lets contributors overwrite published content

published 2026-10-20 20 d ago modified 2026-10-21 18 d ago also GHSA-jf5h-36mg-rp6x , EUVD-2026-105107

cvss: 6.5; version 3.1, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 0.3%; EPSS 0.3% chance of exploitation in 30 days, percentile 27%
public exploits: 0; none known

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.

Patch / fix

fixed in 1 links 3

npm @apostrophecms/import-export 3.7.1

CISA SSVC

Exploitation: none
Automatable: no
Technical impact: partial
Assessed: 20 d ago (2026-10-20)

Exploit prediction

0.34% chance of exploitation in the next 30 days, higher than 27% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by	version	score	vector
CNA	3.1	6.5	CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N
GitHub	3.1	6.5	CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N

Affected packages

ecosystem	package	affected	fixed in
npm	@apostrophecms/import-export	<3.7.1	3.7.1

Affected products

apostrophecms apostrophe
@apostrophecms mport-export

Classification

Weakness

CWE-863 Incorrect Authorization

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

Summary