CVE-2026-31832
Broken Object-Level Authorization in Umbraco Backoffice API Allows Unauthorized Domain Assignment
Publication date: 2026-03-10
Last updated on: 2026-03-18
Assigner: GitHub, Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| umbraco | umbraco_cms | From 17.0.0 (inc) to 17.2.2 (exc) |
| umbraco | umbraco_cms | From 14.0.0 (inc) to 16.5.1 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-639 | The system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability exists in Umbraco, an ASP.NET CMS, in versions from 14.0.0 to before 16.5.1 and 17.2.2. It is a broken object-level authorization issue in a backoffice API endpoint. Authenticated users can assign domain-related data to content nodes without proper authorization checks. This means users can set domains on content nodes they do not have permission to access, bypassing user group privileges or start node restrictions.
How can this vulnerability impact me? :
The impact of this vulnerability is that authenticated users with limited permissions can modify domain-related data on content nodes they should not have access to. This can lead to unauthorized changes in the content management system, potentially affecting the integrity and management of website content. The CVSS score of 5.4 indicates a medium severity with low attack complexity but requiring privileges.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
How can this vulnerability be detected on my network or system? Can you suggest some commands?
I don't know
What immediate steps should I take to mitigate this vulnerability?
To mitigate this vulnerability, you should upgrade Umbraco to version 16.5.1 or 17.2.2 where the issue is fixed.
Ensure that proper authorization checks are enforced on the backoffice API endpoints to prevent unauthorized domain assignments to content nodes.