CVE-2026-32267
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedCraft 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceCraft CMS contains a privilege escalation vulnerability in UsersController->actionImpersonateWithToken where a low-privilege user or unauthenticated user with a shared URL can obtain admin-level privileges. The vulnerability affects versions 4.0.0-RC1 through 4.17.5 and 5.0.0-RC1 through 5.9.11.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data>= 4.0.0.1, < 4.17.6>= 5.0.1, < 5.9.12= 4.0.0= 5.0.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify installed Craft CMS versionLocate the composer.json file in your project root and find the 'craftcms/cms' version entry, or log into the admin panel and navigate to Utilities → System Report to view the installed versionAffected if The installed version falls within 4.0.0-RC1 through 4.17.5, 5.0.0-RC1 through 5.9.11, or matches exactly 4.0.0 or 5.0.0
-
Confirm user sharing or public registration is activeIn the Craft CMS admin panel, go to Settings → Users → Settings and check whether the 'Allow public registration' or user sharing features are enabledAffected if User sharing or public registration is turned on in a vulnerable version
-
Audit admin-level user accountsIn the admin panel, navigate to Users → Admins and review all accounts with admin privileges for any unrecognized or recently created accountsAffected if There are admin accounts that were not created by your known administrators
-
Inspect server access logs for impersonation endpoint activitySearch your web server access logs (typically in /var/log/apache2 or /var/log/nginx) for requests to paths such as /users/impersonate-with-token or any unusual /users controller actionsAffected if Unrecognized or suspicious requests to the impersonation functionality appear in the logs
You are affected if your Craft CMS version is within the vulnerable ranges AND user sharing or public registration features are enabled, allowing the impersonation token flaw to be exploited.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped4.17.65.9.12
Upgrade Craft CMS to version 4.17.6 or later, or 5.9.12 or later. If immediate patching is not possible, review and restrict access to the impersonation functionality through web server configuration or access controls.
Craft CMS 4.17.6 or 5.9.12 (depending on your major version)
- Backup your Craft CMS database and files before upgrading
- Ensure you have a recent database backup
- Upgrade to Craft CMS 4.17.6 if you are on the 4.x line
- Upgrade to Craft CMS 5.9.12 if you are on the 5.x line
- After upgrading, verify that the UsersController->actionImpersonateWithToken endpoint properly validates authorization
- Test that low-privilege users cannot escalate to admin privileges
- Clear any caches after upgrading (Craft CP -> Utilities -> Clear Caches)
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-32267 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-32267 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data