How severe is CVE-2026-33162?

No CVSS score has been assigned to CVE-2026-33162 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2026-33162?

CVE-2026-33162 affects the following packages: craftcms/cms (Packagist). Ecosystems affected: Packagist.

How do I fix CVE-2026-33162?

Update craftcms/cms to 5.9.14 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-33162 is resolved across your whole dependency graph.

How do I detect CVE-2026-33162 in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for craftcms/cms, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2026-33162 if there is no patch (or I can't update yet)?

Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Is CVE-2026-33162 actively exploited in the wild?

No public exploit code has been indexed for CVE-2026-33162 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2026-33162?

CVE-2026-33162 has an EPSS (Exploit Prediction Scoring System) score of 0.3%, placing it in the 22th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2026-33162?

CVE-2026-33162 is classified as CWE-285 (CWE-285), CWE-862 (CWE-862). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2026-33162 published, and has it been updated?

CVE-2026-33162 was published on March 24, 2026 and was last updated on October 28, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐘 Packagist

Not in CISA KEV

CVE-2026-33162 — cms

Fix: craftcms/cms@3c1ab1c

CVE-2026-33162 is a CWE-285 vulnerability in craftcms/cms. A fix is available for craftcms/cms — see the affected versions and patch details below.

Craft CMS: Authorization bypass in "entries/move-to-section" allows control panel user to move entries without section permissions

Also known asGHSA-f582-6gf6-gx4g

Published

Mar 24, 2026

Updated

Oct 28, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Oct 29, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2026-33162.

EPSS Exploitation Probability

via FIRST.org ↗

0.3%probability of exploitation in next 30 days

Lower Risk-0.08%

Lower risk than most CVEs22th percentile — riskier than 22% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected

🐘craftcms/cms

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.

Description

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

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 actionMoveToSectionModalData for 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.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`craftcms/cms`	≥ 5.3.0&&< 5.9.14	5.9.14`composer require craftcms/cms:^5.9.14`

Affected Products

1 product · 1 configurations

Application

craft cmscraftcms

≥ 5.3.0 && < 5.9.14

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for craftcms/cms, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update craftcms/cms to 5.9.14 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-33162 is resolved across your whole dependency graph.
Workarounds
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Frequently Asked Questions

### 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 authoriza

O3 Security · Impact-Aware SCA

Is CVE-2026-33162 in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works