Servers and applications
GHSA-348f-9mg8-rhv4
Sensitive member property values exposed through the Examine members index
- Severity
- Medium 4.9
- Published
- 17 Nov 2026
- Last changed
- 17 Nov 2026
- Added to UpHeron
- 17 Nov 2026
- Fixed in
- 17.8.2
- Attack
- Over the network · Needs an administrator account · No user action needed
- Attacker can
- Read data
- CVSS vector
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N- Sources
- Project advisories (GitHub)
Description
Member properties marked as "Is sensitive" are intended to be visible only to backoffice users in the Sensitive data user group. Since Umbraco 17.4.0, the values of these properties were included in the members Examine index. A backoffice user with access to the Settings and Members sections, but who was not in the Sensitive data group, could read these values by searching the members index from the Examine Management dashboard, or by calling the corresponding Management API endpoint directly.
The user has to be authenticated to the backoffice. The same user is correctly prevented from seeing sensitive values when viewing or editing the member, and when retrieving the member through the Management API. The issue only allows sensitive values to be read; it doesn't let anyone change member data.
Because the values were stored in the members index itself, custom code on a site that queries the members index and returns all of its fields could also expose them.
Workarounds
Until you can upgrade, either add backoffice users who have access to both the Settings and Members sections to the Sensitive data group, or remove one of those sections from their user groups.
If your site has custom code that queries the members index, make sure it only returns the fields it needs.
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-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
- CVE-2026-117553Umbraco CMS before 17.7.2 and 18.2.2 Account Takeover via Host Header PoisoningHigh 7.7 27 Oct 2026
References
- GitHub Advisory Database https://github.com/advisories/GHSA-348f-9mg8-rhv4
- github.com https://github.com/umbraco/Umbraco-CMS/security/advisories/GHSA-348f-9mg8-rhv4