CVE-2026-113649 Details
Description
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.
A vulnerability exists in ApostropheCMS versions prior to 3.7.1 in the import-export module and 4.34.0 in the core application. The issue allows editors to manipulate published content of certain types without proper authorization. Specifically, an editor could import or update published documents of a type whose publication is restricted to a higher role, such as admin. This exploitation takes advantage of a gap in the permission checks during the import process, where the normal publication lifecycle and authorization were not enforced, leading to unauthorized changes in the content's public state.
This vulnerability has been addressed in ApostropheCMS version 4.34.0 and in the import-export module version 3.7.1.
Metrics
CVSS 4.0 Severity and Vector Strings:
VolerionCVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
Volerion
Assessed Oct 20, 2026CISA-ADP
Assessed Oct 23, 2026References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| CWE-862 | Missing Authorization | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| ApostropheCMS | < 4.34.0 (semver) |
CPE
Remediation
| |
| ApostropheCMS import-export | < 3.7.1 (semver) |
CPE
Remediation
| |
Change History
2 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Oct 23, 2026 | CVE Modified | CISA-ADP |
| Oct 20, 2026 | New CVE Received | [email protected] |