ApostropheCMS: Import API bypasses publication roles for protected content

published 2026-10-20 19 d ago modified 2026-10-23 17 d ago also GHSA-5m22-7pfq-vp65 , EUVD-2026-105184

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 22%
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 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.

Patch / fix

fixed in 2 links 5

npm @apostrophecms/import-export 3.7.1
npm apostrophe 4.34.0

CISA SSVC

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

Exploit prediction

0.30% chance of exploitation in the next 30 days, higher than 22% 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
npm	apostrophe	<4.34.0	4.34.0

Affected products

apostrophecms apostrophe
@apostrophecms import-export

Classification

Weakness

CWE-862 Missing 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