CVE-2026-31832: Umbraco Backoffice API Allows Unauthorized Modification of Domain Data

Published Mar 10, 2026
·
Updated

Description A broken object-level authorization vulnerability exists in a backoffice API endpoint that allows authenticated users to assign domain-related data to content nodes without proper authorization checks.

The issue is caused by insufficient authorization enforcement on the affected API endpoint, whereby via an API call, domains can be set on content nodes that the editor does not have permission to access (either via user group privileges or start nodes).

Impact An attacker can modify domain configurations for content nodes they are not permitted to edit. This may result in malicious or unintended routing behaviour, service disruption, and potential disclosure of configuration-related information.

Patches The issue is patched in 16.5.1 and 17.2.2.

Workarounds There is no workaround other than upgrading.

Other sources

Umbraco is an ASP.NET CMS. From 14.0.0 to before 16.5.1 and 17.2.2, A broken object-level authorization vulnerability exists in a backoffice API endpoint that allows authenticated users to assign domain-related data to content nodes without proper authorization checks. The issue is caused by insufficient authorization enforcement on the affected API endpoint, whereby via an API call, domains can be set on content nodes that the editor does not have permission to access (either via user group privileges or start nodes). This vulnerability is fixed in 16.5.1 and 17.2.2.

MITRE

Affected Software

5 affected componentsFixes available
npm/umbraco>14.0.0<=16.5.1, <17.2.2
nuget/Umbraco.Cms>=17.0.0<17.2.2
17.2.2
nuget/Umbraco.Cms>=14.0.0<16.5.1
16.5.1
Umbraco Umbraco CMS>=14.0.0<16.5.1
Umbraco Umbraco CMS>=17.0.0<17.2.2

Event History

Mar 10, 2026
CVE Published
via MITRE·09:49 PM
Data Sourced
via MITRE·09:49 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·10:16 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·10:16 PM
Affected Software
Mar 11, 2026
Advisory Published
via GitHub·12:24 AM
Data Sourced
via GitHub·12:24 AM
DescriptionSeverityWeaknessAffected Software
Jul 22, 58183
Event
via FIRST·03:33 AM

Frequently Asked Questions

1

What is the severity of CVE-2026-31832?

CVE-2026-31832 has been classified as a high severity vulnerability due to its potential for unauthorized modification of domain data.

2

How do I fix CVE-2026-31832?

To fix CVE-2026-31832, upgrade Umbraco to the latest version, specifically version 16.5.1 or 17.2.2 and later.

3

What versions of Umbraco are affected by CVE-2026-31832?

CVE-2026-31832 affects Umbraco versions from 14.0.0 to before 16.5.1 and from 17.2.2 and earlier.

4

What type of vulnerability is CVE-2026-31832?

CVE-2026-31832 is a broken object-level authorization vulnerability that allows unauthorized access to domain-related data in the backoffice API.

5

Can authenticated users exploit CVE-2026-31832?

Yes, authenticated users can exploit CVE-2026-31832 to modify domain data due to insufficient authorization checks in the API.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203