Servers and applications
GHSA-w5q3-9wf8-43gg
Insufficient authorization on Management API search endpoints
- Severity
- Medium 6.5
- Published
- 18 Aug 2026
- Last changed
- 18 Aug 2026
- Added to UpHeron
- 3 Nov 2026
- Fixed in
- 17.6.2, 18.1.1
- Attack
- Over the network · Needs a user account · No user action needed
- Attacker can
- Read data
- CVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N- Sources
- Project advisories (GitHub)
Description
A group of Management API endpoints relating to search indexing require only that the caller be an authenticated backoffice user. They do not apply the section-level authorization check that comparable administrative endpoints apply, and they do not filter their results against the calling user's permissions. Equivalent functionality in Umbraco 13 was correctly restricted; the check was lost when these endpoints were reimplemented.
A backoffice user with any level of access, including the lowest-privilege built-in groups, and users restricted to a single content branch, can retrieve content, media and member data well beyond what their permissions allow. This includes unpublished content and content protected by Public Access, and it bypasses the "sensitive data" user-group permission for member records. The exposure of member data is greater on 17.x and 18.x than on earlier affected versions. No integrity impact.
Workarounds
There is no configuration setting that disables these endpoints. Where the affected functionality is not needed, access to the Management API search and index routes can be restricted at a reverse proxy or WAF; this also disables the corresponding Settings dashboard for administrators. Otherwise, review who holds backoffice accounts, enforce MFA, and rotate credentials for any account that cannot be vouched for. Rebuilding search indexes does not mitigate the issue.
Affected software
| Software | Affected versions |
|---|---|
Umbraco CMSServers and applications · github:umbraco/umbraco-cms |
|
About Umbraco CMS
open-source CMS
- Total downloads (NuGet)
- 8,485,226NuGet, 15 Nov 2026
- GitHub stars
- 5,286GitHub, 15 Nov 2026
- Forks
- 2,951GitHub, 15 Nov 2026
- Latest release
- release-18.3.1GitHub, 15 Nov 2026
- Released
- 5 Nov 2026GitHub
- Developer
- UmbracoWikidata
- License
- MIT LicenseWikidata
- Written in
- C#Wikidata
- First published on GitHub
- 10 Jun 2013GitHub
Release lines
| Release | Latest | Security fixes |
|---|---|---|
| 18 | 18.3.1 | Until 25 Jun 2027 |
| 17 (LTS)LTS | 17.8.1 | Until 27 Nov 2028 |
| 16 | 16.5.1 | Ended 12 Jun 2026 |
| 15 | 15.4.4 | Ended 14 Nov 2025 |
| 14 | 14.3.4 | Ended 30 May 2025 |
| 13 (LTS)LTS | 13.16.4 | Until 14 Dec 2026 |
From endoflife.date.
Vulnerabilities in Umbraco CMS
- In our list
- 79
- Published in the last 12 months
- 30
- Critical, last 12 months
- 1
- High, last 12 months
- 6
- Known exploited
- 0
- GHSA-348f-9mg8-rhv4Sensitive member property values exposed through the Examine members indexMedium 4.9 17 Nov 2026
- GHSA-5pr6-xx84-wp49Incomplete fix for CVE-2026-69197: Delivery API can still expose protected (Public Access) content referenced through pickersMedium 5.3 17 Nov 2026
- CVE-2026-130068Umbraco CMS 17.0.0 before 17.7.1 and 18.0.0 before 18.2.1 Authorization Bypass via Document Version APIMedium 5.3 16 Nov 2026
- GHSA-8h2h-5qxc-35c7v7 XLTS: Missing authentication on Canvas Designer lets anonymous users create, overwrite and delete site style filesHigh 7.5 13 Nov 2026
- GHSA-34cf-fv2h-gwmqv7/v8 XLTS: Back-office login response timing reveals whether a username existsMedium 5.3 13 Nov 2026
- GHSA-48p5-4fgv-rrjwv7/v8 XLTS: Back-office login checks the password before account lockout, weakening brute-force protectionMedium 6.5 13 Nov 2026
References
- GitHub Advisory Database https://github.com/advisories/GHSA-w5q3-9wf8-43gg
- github.com https://github.com/umbraco/Umbraco-CMS/security/advisories/GHSA-w5q3-9wf8-43gg