ApostropheCMS: Import API bypasses publication roles for protected 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. 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. ## Import API bypasses publication roles for protected content The import gate in canImportOrExport() checks the type'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. The reported security boundary is a content type that an editor may edit but whose publication is reserved for a stronger role. Direct public-
- Products
- @apostrophecms/import-export, apostrophe
- Affected versions
- Not specified
- Fixed versions
- 3.7.1, 4.34.0
- CVEs
- CVE-2026-113649
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 31 Oct 2026, 15:24 UTC · Revision 1
Source evidence
ApostropheCMS: Import API bypasses publication roles for protected content
core-osv · Original sourcePublished 21 Oct 2026, 17:03 UTC
## 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. 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. ## Import API bypasses publication roles for protected content The import gate in canImportOrExport() checks the type'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. The reported security boundary is a content type that an editor may edit but whose publication is reserved for a stronger role. Direct public-
osv:GHSA-5m22-7pfq-vp65
@apostrophecms/import-export
Fixed versions: 3.7.1
apostrophe
Fixed versions: 4.34.0
Complete source record
{
"id": "050ea7c5536007e7affa2f123124b7fdfdc828b291a30e5c538eca671b49154e",
"url": "https://osv.dev/vulnerability/GHSA-5m22-7pfq-vp65",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "ApostropheCMS: Import API bypasses publication roles for protected content",
"summary": "## 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. 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. ## Import API bypasses publication roles for protected content The import gate in canImportOrExport() checks the type'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. The reported security boundary is a content type that an editor may edit but whose publication is reserved for a stronger role. Direct public-",
"evidence": "osv:GHSA-5m22-7pfq-vp65",
"products": [
{
"name": {
"value": "@apostrophecms/import-export",
"evidence": "/affected/0/package/name"
},
"prerequisites": [],
"fixed_versions": [
{
"value": "3.7.1",
"evidence": "/affected/0/ranges"
}
],
"affected_versions": []
},
{
"name": {
"value": "apostrophe",
"evidence": "/affected/1/package/name"
},
"prerequisites": [],
"fixed_versions": [
{
"value": "4.34.0",
"evidence": "/affected/1/ranges"
}
],
"affected_versions": []
}
],
"severity": "medium",
"structured": {
"id": "GHSA-5m22-7pfq-vp65",
"aliases": [
"CVE-2026-113649",
"GHSA-5m22-7pfq-vp65"
],
"metrics": [
{
"type": "CVSS_V3",
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N"
}
],
"affected": [
{
"ranges": [
{
"type": "SEMVER",
"events": [
{
"introduced": "0"
},
{
"fixed": "3.7.1"
}
]
}
],
"package": {
"name": "@apostrophecms/import-export",
"purl": "pkg:npm/%40apostrophecms/import-export",
"ecosystem": "npm"
},
"database_specific": {
"source": "https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2026/10/GHSA-5m22-7pfq-vp65/GHSA-5m22-7pfq-vp65.json"
}
},
{
"ranges": [
{
"type": "SEMVER",
"events": [
{
"introduced": "0"
},
{
"fixed": "4.34.0"
}
]
}
],
"package": {
"name": "apostrophe",
"purl": "pkg:npm/apostrophe",
"ecosystem": "npm"
},
"database_specific": {
"source": "https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2026/10/GHSA-5m22-7pfq-vp65/GHSA-5m22-7pfq-vp65.json"
}
}
],
"modified": "2026-10-21T17:15:08.642595575Z",
"provider": "osv",
"references": [
"https://github.com/apostrophecms/apostrophe/security/advisories/GHSA-5m22-7pfq-vp65",
"https://nvd.nist.gov/vuln/detail/CVE-2026-113649",
"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/%40apostrophecms/import-export%403.7.1",
"https://github.com/apostrophecms/apostrophe/releases/tag/@apostrophecms/import-export@3.7.1",
"https://github.com/apostrophecms/apostrophe/releases/tag/apostrophe@4.34.0"
],
"provider_metadata": {
"cwe_ids": [
"CWE-862"
],
"severity": "MODERATE",
"github_reviewed": true,
"nvd_published_at": "2026-10-20T17:17:35Z",
"github_reviewed_at": "2026-10-21T17:03:03Z"
}
},
"related_cves": [
{
"value": "CVE-2026-113649",
"evidence": "/aliases"
}
],
"security_relevant": true,
"severity_evidence": "/severity/0/score"
},
"source_id": "core-osv",
"document_id": 397040,
"published_at": "2026-10-21T17:03:03+00:00"
}