Theme Editor AJAX handlers in the CMS section do not enforce per-template-type permission checks. While the CMS controller `CmsControllersIndex` uses OR-logic across five permissions (`cms.manage pages`, `cms.manage partials`, `cms.manage layouts`, `cms.manage content`, `cms.manage assets`) to grant access to the section, individual handlers such as `onSave()`, `onDelete()`, and `onDeleteTemplates()` fail to verify if the user possesses the specific permission for the requested template type. This allows an authenticated backend user with any single CMS permission to perform unauthorized actions, such as deleting layouts, modifying partials, or reading content files. Additionally, the `AssetList` widget is registered for any user passing the controller gate regardless of the `cms.manage assets` permission, and its `onUpload()` handler lacks the theme-validation call used by other mutating handlers, enabling unauthorized file uploads into the active theme's asset directory.