GHSA-f582-6gf6-gx4g

### Summary An authenticated control panel user with only accessCp can move entries across sections via POST `/actions/entries/move-to-section`, even when they do not have `saveEntries:{sectionUid}` permission for either source or destination section. ### Details #### Root-cause analysis 1. actionMoveToSection accepts sectionId and entryIds, loads entries, and iterates: `Craft::$app->getEntries()->moveEntryToSection($entry, $section)`. 2. The endpoint does not enforce per-entry or per-section authorization checks. 3. `moveEntryToSection()` also does not enforce current-user authorization. 4. There is a permission check in `actionMoveToSectionModalData` for building UI options, but that check is not enforced in the actual endpoint. 5. Therefore, a direct POST request can bypass UI filtering and perform unauthorized entry moves. ### Impact * This is an authorization bypass permitting unauthorized content changes. * Authenticated low-privileged control panel users can move entries they should not be able to manage, violating integrity and potentially disrupting routing/editorial controls.