{"answers":{"affected":"2 open source packages ship an affected version, including craftcms/cms.","exploited":"There is no known exploitation of CVE-2026-50280 in the wild and no public exploit code.","fix":"Upgrade craftcms/cms to 5.9.21 or later.","what":"CVE-2026-50280 is a medium-severity missing authorization vulnerability in craftcms cms, published on 1 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-50280 and fix it if it is affected.\n\nWhat it is: CVE-2026-50280 is a medium-severity missing authorization vulnerability in craftcms cms, published on 1 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-50280 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- craftcms/cms (Packagist): affected from 5.0.0-RC1; fixed in 5.9.21\n- craftcms/cms (Packagist): affected from 5.0.0-RC1; fixed in 5.9.21\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-50280/ (Markdown: https://insights.sbomify.com/CVE-2026-50280/index.md)","id":"CVE-2026-50280","markdown":"https://insights.sbomify.com/CVE-2026-50280/index.md","name":"CVE-2026-50280","record":{"aliases":["GHSA-43cq-c2gq-pfpw"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_modify","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Craft CMS","requires_auth":"low_privilege","summary":"Low-privileged users can move entries into protected sections they cannot write to, bypassing section-level authorization controls in Craft CMS.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":6,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-284","name":"Improper Access Control"}],"description":"Craft CMS is a content management system (CMS). In versions 5.0.0-RC1 and above prior to 5.9.21, the EntriesController::actionMoveToSection() endpoint gates the destination section only by viewEntries:$section-\u003euid rather than requiring saveEntries permission (the source entry is separately checked via Entry::canMove()). As a result, a low-privileged authenticated control-panel user who can move an entry out of its current section can call moveEntryToSection() to rewrite the entry's sectionId and save it into a section where they have read access but no write access. This breaks the section-level authorization model, letting a user with limited permissions inject content into a protected section and interfere with editorial boundaries, approval workflows, and section-specific business logic. This issue has been fixed in version 5.9.21.","ecosystems":["Packagist"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Craft CMS: Authorization bypass in `entries/move-to-section` via missing target-section save check","id":"CVE-2026-50280","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Packagist","product":null,"products":[],"type":"missing_authorization","year":"2026"},"n_packages":2,"n_references":2,"next":{"headline":"Craft CMS: Mass assignment via id in newAttributes during bulk duplicate overwrites existing elements","id":"CVE-2026-50281"},"packages":[{"ecosystem":"Packagist","fixed":["5.9.21"],"introduced":["5.0.0-RC1"],"last_affected":[],"package":"craftcms/cms","purl":null,"source":"GHSA-43cq-c2gq-pfpw"},{"ecosystem":"Packagist","fixed":["5.9.21"],"introduced":["5.0.0-RC1"],"last_affected":[],"package":"craftcms/cms","purl":"pkg:composer/craftcms/cms","source":"GHSA-43cq-c2gq-pfpw"}],"prev":{"headline":"Craft CMS: Authorship spoofing in `entries/save-entry` via pre-check/post-mutation authorization gap","id":"CVE-2026-50279"},"products":["cms"],"published":"2026-07-01","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-07-02","vendors":["craftcms"]},"summary":"Low-privileged users can move entries into protected sections they cannot write to, bypassing section-level authorization controls in Craft CMS.","url":"https://insights.sbomify.com/CVE-2026-50280/"}