CVE-2026-29179: October CMS: Editor Sub-Permission Bypass for Asset and Blueprint File Operations
Fine-grained sub-permission checks for asset and blueprint file operations were not enforced in the CMS and Tailor editor extensions. This only affects backend users who were explicitly granted editor access but had editor.cmsassets or editor.tailorblueprints specifically withheld, an uncommon permission configuration.
Published Apr 21, 2026 · Updated Apr 24, 2026
Affected packages
october/system
- Ecosystem
- Composer (PHP)
- Affected
- >= 4.0.0, < 4.1.16
- Fixed in
- 4.1.16
- Check
composer show october/system
october/system
- Ecosystem
- Composer (PHP)
- Affected
- < 3.7.16
- Fixed in
- 3.7.16
- Check
composer show october/system
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Fine-grained sub-permission checks for asset and blueprint file operations were not enforced in the CMS and Tailor editor extensions. This only affects backend users who were explicitly granted editor access but had editor.cms_assets or editor.tailor_blueprints specifically withheld, an uncommon permission configuration. In this edge case, such users could perform file operations (create, delete, rename, move, upload) on theme assets or blueprint files despite lacking the required sub-permission. A related operator precedence error in the Tailor navigation also disclosed the theme blueprint directory tree under the same conditions.
Impact
- Only exploitable by authenticated backend users with
editoraccess who have been specifically denied theeditor.cms_assetsoreditor.tailor_blueprintssub-permissions - Does not affect default permission configurations where editor users typically have all sub-permissions granted
- Users without
editor.cms_assetscould manipulate theme asset files (delete, rename, move, upload, create directories) - Users without
editor.tailor_blueprintscould manipulate blueprint files (delete, rename, move, upload, create directories) - Users without
editor.tailor_blueprintscould view the theme blueprint navigation tree, disclosing file paths and directory structure
Patches
The vulnerability has been patched in v3.7.16 and v4.1.16. Fine-grained document type permission checks are now enforced on all asset and blueprint file operation commands, and the navigation node condition logic has been corrected. All users are encouraged to upgrade to the latest patched version.
Workarounds
- Restrict the
editorpermission to fully trusted administrators only - Remove the
editorpermission from any user who should not have asset or blueprint management access
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More Composer (PHP) vulnerabilities
All Composer (PHP) entriesCVE-2026-46696
October CMS: Safe Mode Sandbox Bypass via Session Store and Forwarded Builder Calls
low3.3Sep 14, 2026CVE-2026-49400
October CMS: PHP Object Injection via Backend Widget Session Storage
low3.3Sep 14, 2026CVE-2026-26067
October CMS has Safe Mode Bypass via CSS Preprocessor Compilers
medium4.9Apr 21, 2026CVE-2026-27937
October CMS: Reflected XSS via DataTable Form Widget
low3.1No fixApr 21, 2026CVE-2026-24906
October CMS has Stored XSS in Backend Editor Markup Classes
medium5.4Apr 14, 2026CVE-2026-24907
October CMS has Stored XSS in Event Log Mail Preview
medium5.4Apr 14, 2026
