CVE-2026-31834
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 · uneditedUmbraco is an ASP.NET CMS. From 15.3.1 to before 16.5.1 and 17.2.2, A privilege escalation vulnerability has been identified in Umbraco CMS. Under certain conditions, authenticated backoffice users with permission to manage users, may be able to elevate their privileges due to insufficient authorization enforcement when modifying user group memberships. The affected functionality does not properly validate whether a user has sufficient privileges to assign highly privileged roles. This vulnerability is fixed in 16.5.1 and 17.2.2.
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 confidenceAuthenticated backoffice users with permission to manage users can elevate their privileges by assigning themselves to highly privileged roles. The vulnerability stems from insufficient authorization enforcement in the user group membership modification functionality, which fails to validate whether the requesting user has sufficient privileges to assign high-privileged roles.
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>= 15.3.1, < 16.5.1>= 17.0.0, < 17.2.2CVSS 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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/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.
-
Check installed Umbraco CMS versionLocate the version file or check the assembly version in the deployed Umbraco installation. Common locations: ~/web.config or the Umbraco Cms assembly version.Affected if The installed version falls within the affected ranges: >= 15.3.1 and < 16.5.1, OR >= 17.0.0 and < 17.2.2
-
Identify users with user management permissionQuery the backoffice user permissions in the Umbraco database (Users2UserGroup table) or via the backoffice Users section to find accounts that have permission to manage users.Affected if Any non-administrator backoffice user account has permission to access and modify user group memberships
-
Review high-privileged role assignmentsExamine the assigned roles for all backoffice users, particularly looking for assignments to the 'Administrators' or other highly privileged roles in the Users2UserGroup table.Affected if Any backoffice user (other than the built-in administrator) is assigned to a high-privilege role such as Administrators or has more permissions than expected for their job function
You are affected if your Umbraco CMS version is within the vulnerable ranges AND any backoffice user has user management permissions, making privilege escalation possible.
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 · scoped16.5.117.2.2
Upgrade Umbraco CMS to version 16.5.1 or 17.2.2 or later. If immediate patching is not feasible, strictly limit user management permissions to only the most trusted administrators and audit existing user role assignments.
Umbraco CMS 16.5.1 or 17.2.2 (depending on your major version branch)
- Identify your current Umbraco CMS version by checking the Umbraco backoffice (Settings > About) or your project configuration
- If you are on Umbraco CMS version 15.x or 16.x (versions 16.0.0 through 16.5.0), upgrade to version 16.5.1
- If you are on Umbraco CMS version 17.x (versions 17.0.0 through 17.2.1), upgrade to version 17.2.2
- Follow the official Umbraco upgrade documentation for your specific version path to perform the upgrade
- After upgrading, verify the version number in the Umbraco backoffice (Settings > About) shows 16.5.1 or 17.2.2
- Test that user group membership modifications now properly enforce authorization checks
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing4.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 $3,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-31834 — 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-31834 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