{ "document": { "category": "csaf_base", "csaf_version": "2.0", "distribution": { "tlp": { "label": "WHITE" } }, "lang": "en", "notes": [ { "category": "legal_disclaimer", "text": "The Netherlands Cyber Security Center (henceforth: NCSC-NL) maintains this portal to enhance access to its information and vulnerabilities. The use of this information is subject to the following terms and conditions:\n\nThe vulnerabilities disclosed in this portal are gathered by NCSC-NL from a variety of open sources, which the user can retrieve from other platforms. NCSC-NL makes every reasonable effort to ensure that the content of this portal is kept up to date, and that it is accurate and complete. Nevertheless, NCSC-NL cannot entirely rule out the possibility of errors, and therefore cannot give any warranty in respect of its completeness, accuracy or real-time keeping up-to-date. NCSC-NL does not control nor guarantee the accuracy, relevance, timeliness or completeness of information obtained from these external sources. The vulnerabilities disclosed in this portal are intended solely for the convenience of professional parties to take appropriate measures to manage the risks posed to the cybersecurity. No rights can be derived from the information provided therein.\n\nNCSC-NL and the Kingdom of the Netherlands assume no legal liability or responsibility for any damage resulting from either the use or inability of use of the vulnerabilities disclosed in this portal. This includes damage resulting from the inaccuracy of incompleteness of the information contained in it.\nThe information on this page is subject to Dutch law. All disputes related to or arising from the use of this portal regarding the disclosure of vulnerabilities will be submitted to the competent court in The Hague. This choice of means also applies to the court in summary proceedings." } ], "publisher": { "category": "coordinator", "contact_details": "cert@ncsc.nl", "name": "National Cyber Security Centre", "namespace": "https://www.ncsc.nl/" }, "title": "CVE-2026-32267", "tracking": { "current_release_date": "2026-03-23T14:02:43.701636Z", "generator": { "date": "2026-02-17T15:00:00Z", "engine": { "name": "V.E.L.M.A", "version": "1.7" } }, "id": "CVE-2026-32267", "initial_release_date": "2026-03-16T19:38:39.130910Z", "revision_history": [ { "date": "2026-03-16T19:38:39.130910Z", "number": "1", "summary": "CVE created.| Source created.| CVE status created. (valid)| Description created for source.| CVSS created.| Products created (2).| References created (2).| CWES updated (1)." }, { "date": "2026-03-16T19:38:46.799053Z", "number": "2", "summary": "NCSC Score created." }, { "date": "2026-03-16T19:42:10.148210Z", "number": "3", "summary": "Source created.| CVE status created. (valid)| Description created for source.| CVSS created.| References created (3).| CWES updated (1)." }, { "date": "2026-03-16T19:42:13.660376Z", "number": "4", "summary": "NCSC Score updated." }, { "date": "2026-03-16T20:26:50.079718Z", "number": "5", "summary": "Source created.| CVE status created. (valid)| Description created for source.| CVSS created.| References created (2).| CWES updated (1)." }, { "date": "2026-03-16T20:26:55.137641Z", "number": "6", "summary": "NCSC Score updated." }, { "date": "2026-03-16T22:50:57.455839Z", "number": "7", "summary": "References created (1)." }, { "date": "2026-03-17T07:35:01.624468Z", "number": "8", "summary": "NCSC Score updated." }, { "date": "2026-03-17T15:00:25.203168Z", "number": "9", "summary": "Source created.| CVE status created. (valid)| EPSS created." }, { "date": "2026-03-17T15:39:03.011376Z", "number": "10", "summary": "Unknown change." }, { "date": "2026-03-17T15:39:51.919397Z", "number": "11", "summary": "CVSS updated." }, { "date": "2026-03-17T15:40:01.609407Z", "number": "12", "summary": "NCSC Score updated." }, { "date": "2026-03-17T16:31:50.777344Z", "number": "13", "summary": "CVSS updated." }, { "date": "2026-03-17T16:31:57.509178Z", "number": "14", "summary": "NCSC Score updated." }, { "date": "2026-03-17T16:38:53.322123Z", "number": "15", "summary": "CVSS updated." }, { "date": "2026-03-17T18:25:38.567665Z", "number": "16", "summary": "CVSS created.| Products created (2).| Product Identifiers created (8).| Products connected (6).| Exploits created (1)." }, { "date": "2026-03-17T18:25:43.585812Z", "number": "17", "summary": "NCSC Score updated." }, { "date": "2026-03-18T17:39:09.571838Z", "number": "18", "summary": "Unknown change." }, { "date": "2026-03-18T17:39:22.197075Z", "number": "19", "summary": "NCSC Score updated." }, { "date": "2026-03-19T15:31:14.947045Z", "number": "20", "summary": "Source created.| CVE status created. (valid)| Description created for source.| CVSS created.| References created (4).| CWES updated (1)." }, { "date": "2026-03-19T15:31:16.792035Z", "number": "21", "summary": "NCSC Score updated." }, { "date": "2026-03-20T09:31:21.987316Z", "number": "22", "summary": "Source connected.| CVE status created. (valid)| EPSS created." } ], "status": "interim", "version": "22" } }, "product_tree": { "branches": [ { "branches": [ { "branches": [ { "category": "product_version_range", "name": "vers:unknown/4.0.0", "product": { "name": "vers:unknown/4.0.0", "product_id": "CSAFPID-909152", "product_identification_helper": { "cpe": "cpe:2.3:a:craftcms:craft_cms:4.0.0:-:*:*:*:*:*:*" } } }, { "category": "product_version_range", "name": "vers:unknown/4.0.0-rc1", "product": { "name": "vers:unknown/4.0.0-rc1", "product_id": "CSAFPID-5379030", "product_identification_helper": { "cpe": "cpe:2.3:a:craftcms:craft_cms:4.0.0:rc1:*:*:*:*:*:*" } } }, { "category": "product_version_range", "name": "vers:unknown/4.0.0-rc2", "product": { "name": "vers:unknown/4.0.0-rc2", "product_id": "CSAFPID-5379031", "product_identification_helper": { "cpe": "cpe:2.3:a:craftcms:craft_cms:4.0.0:rc2:*:*:*:*:*:*" } } }, { "category": "product_version_range", "name": "vers:unknown/4.0.0-rc3", "product": { "name": "vers:unknown/4.0.0-rc3", "product_id": "CSAFPID-5379032", "product_identification_helper": { "cpe": "cpe:2.3:a:craftcms:craft_cms:4.0.0:rc3:*:*:*:*:*:*" } } }, { "category": "product_version_range", "name": "vers:unknown/5.0.0", "product": { "name": "vers:unknown/5.0.0", "product_id": "CSAFPID-1114119", "product_identification_helper": { "cpe": "cpe:2.3:a:craftcms:craft_cms:5.0.0:-:*:*:*:*:*:*" } } }, { "category": "product_version_range", "name": "vers:unknown/5.0.0-rc1", "product": { "name": "vers:unknown/5.0.0-rc1", "product_id": "CSAFPID-5379068", "product_identification_helper": { "cpe": "cpe:2.3:a:craftcms:craft_cms:5.0.0:rc1:*:*:*:*:*:*" } } }, { "category": "product_version_range", "name": "vers:unknown/>=4.0.0.1|<4.17.6", "product": { "name": "vers:unknown/>=4.0.0.1|<4.17.6", "product_id": "CSAFPID-5838463", "product_identification_helper": { "cpe": "cpe:2.3:a:craftcms:craft_cms:*:*:*:*:*:*:*:*" } } }, { "category": "product_version_range", "name": "vers:unknown/>=5.0.1|<5.9.12", "product": { "name": "vers:unknown/>=5.0.1|<5.9.12", "product_id": "CSAFPID-5838464", "product_identification_helper": { "cpe": "cpe:2.3:a:craftcms:craft_cms:*:*:*:*:*:*:*:*" } } } ], "category": "product_name", "name": "Craft Cms" }, { "branches": [ { "category": "product_version_range", "name": "vers:unknown/>=4.0.0-rc1|<4.17.6", "product": { "name": "vers:unknown/>=4.0.0-rc1|<4.17.6", "product_id": "CSAFPID-5830344" } }, { "category": "product_version_range", "name": "vers:unknown/>=5.0.0-rc1|<5.9.12", "product": { "name": "vers:unknown/>=5.0.0-rc1|<5.9.12", "product_id": "CSAFPID-5830345" } } ], "category": "product_name", "name": "cms" } ], "category": "vendor", "name": "Craftcms" } ] }, "vulnerabilities": [ { "cve": "CVE-2026-32267", "cwe": { "id": "CWE-863", "name": "Incorrect Authorization" }, "notes": [ { "category": "description", "text": "Craft CMS is a content management system (CMS). From version 4.0.0-RC1 to before version 4.17.6 and from version 5.0.0-RC1 to before version 5.9.12, a low-privilege user (or an unauthenticated user who has been sent a shared URL) can escalate their privileges to admin by abusing UsersController->actionImpersonateWithToken. This issue has been patched in versions 4.17.6 and 5.9.12.", "title": "cveprojectv5 - https://www.cve.org/CVERecord?id=CVE-2026-32267" }, { "category": "description", "text": "### Summary\nA low-privilege user (or an unauthenticated user who has been sent a shared URL) can escalate their privileges to admin by abusing `UsersController->actionImpersonateWithToken`.\n\nAffected users should update to Craft 4.17.6 and 5.9.12 to mitigate the issue.\n\n### Details\nThis vulnerability allows any low-privilege user to escalate their privileges and become an admin, or, in extreme circumstances, unprivileged users to do the same.\n\nTherefore, this vulnerability affects Craft Pro and Team more than Craft Solo.\n\nSpecifically, an attacker who possesses a valid “preview token” can then append `&action=users/impersonate-with-token&userId=1&prevUserId=1` to the preview URL to hijack the request into the impersonation endpoint, logging in as any user (including admin) without authentication. Getting the preview token is easy, and all an editor would have to do is create a single article, click “Preview”, and then recover this token.\n\nHere’s what happens:\n\n1. The action re-dispatch in `actionPreview()` passes `$skipSpecialHandling=true` to `handleRequest()`, bypassing all security guards, and passes `$checkToken=false` to `checkIfActionRequest()`, which allows an attacker-controlled action query parameter to override the dispatch target.\n2. The `requireToken()` guard on `actionImpersonateWithToken()` only checks a boolean (`_hadToken`) that was set when the preview token was initially resolved. It does not verify that the token was intended for the impersonation action, and so any valid token from any route satisfies the check.\n3. `actionImpersonateWithToken` is listed in `$allowAnonymous` and performs no authorization beyond `requireToken()`, so no prior authentication is required.\n\n### PoC\n\nThe PoC achieves full admin takeover on the latest Craft CMS 5.9.10. Spawn a local version of Craft. Then, you’ll want to log in and create a valid setup:\n\n1. Log in at http://host:18895/admin\n2. Go to Settings,  Sections, New Section (name: \"Blog\", type: \"Channel\")\n3. Under Site Settings, set URI Format to blog/{slug}\n4. Then go to Entries, New Entry, Blog, and give it any title\n\nNext, obtain a preview token\n\n1. Open the saved entry in the editor\n2. Click the Preview button\n3. A preview pane opens with the entry rendered in an iframe\n4. Right-click inside the preview pane and Inspect Element\n5. Find the