Summary
Craft CMS has an authorization bypass which allows any control panel user to move entries without permissions
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
- actionMoveToSection accepts sectionId and entryIds, loads entries, and iterates:
Craft::$app->getEntries()->moveEntryToSection($entry, $section). - The endpoint does not enforce per-entry or per-section authorization checks.
moveEntryToSection()also does not enforce current-user authorization.- There is a permission check in
actionMoveToSectionModalDatafor building UI options, but that check is not enforced in the actual endpoint. - 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.
Impact
The application does not perform an authorization check before performing a sensitive operation. Typical impact: unauthorized access to restricted functionality or data.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
Frequently Asked Questions
- What is CVE-2026-33162? CVE-2026-33162 is a medium-severity missing authorization vulnerability in craftcms/cms (composer), affecting versions >= 5.3.0, <= 5.9.13. It is fixed in 5.9.14. The application does not perform an authorization check before performing a sensitive operation.
- Which versions of craftcms/cms are affected by CVE-2026-33162? craftcms/cms (composer) versions >= 5.3.0, <= 5.9.13 is affected.
- Is there a fix for CVE-2026-33162? Yes. CVE-2026-33162 is fixed in 5.9.14. Upgrade to this version or later.
- Is CVE-2026-33162 exploitable, and should I be worried? Whether CVE-2026-33162 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2026-33162 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2026-33162? Upgrade
craftcms/cmsto 5.9.14 or later.