october/system
Affected
- introduced
4.0.0, fixed4.1.16(ecosystem)
Fixed versions
4.1.16
Fix
The export has no generic command for this ecosystem.
Advisory
Also known as: 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.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
editor access who have been specifically denied the editor.cms_assets or editor.tailor_blueprints sub-permissionseditor.cms_assets could manipulate theme asset files (delete, rename, move, upload, create directories)editor.tailor_blueprints could manipulate blueprint files (delete, rename, move, upload, create directories)editor.tailor_blueprints could view the theme blueprint navigation tree, disclosing file paths and directory structurePatches
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
editor permission to fully trusted administrators onlyeditor permission from any user who should not have asset or blueprint management accessLow Basis: The source's own band: LOW
4.0.0, fixed 4.1.16 (ecosystem)4.1.16
The export has no generic command for this ecosystem.
0, fixed 3.7.16 (ecosystem)3.7.16
The export has no generic command for this ecosystem.
Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0