Servers and applications
GHSA-f7m5-5x7g-2p52
Incorrect authorization lets Content-only backoffice users modify Templates, enabling remote code execution
- Severity
- High 8.8
- Published
- 18 Aug 2026
- Last changed
- 18 Aug 2026
- Added to UpHeron
- 3 Nov 2026
- Fixed in
- 18.1.1
- Attack
- Over the network · Needs a user account · No user action needed
- Attacker can
- Read data · Change data · Take it down
- CVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H- Sources
- Project advisories (GitHub)
Description
An authorization flaw in the Umbraco backoffice (Management API) allows an authenticated backoffice user with limited privileges to perform certain actions that should be restricted to higher-privileged users. Under the default runtime configuration this can result in remote code execution on the server.
An attacker holding a low-privilege, non-administrative backoffice account can carry out a subset of operations normally reserved for higher-privileged users. Under the default runtime mode, this can lead to remote code execution in the context of the web application, potentially resulting in full compromise of the site and the underlying server.
Running the application in Production runtime mode mitigates the code-execution impact, although the underlying authorization weakness is present regardless of mode.
Exploitation requires a valid authenticated backoffice account. There is no unauthenticated path and no self-registration path.
Workarounds
- Configure the application to run in Production runtime mode (Umbraco:CMS:Runtime:Mode = Production) to mitigate the code-execution impact.
- Review which users hold non-administrative backoffice accounts, and audit for unexpected changes to backoffice-managed resources.
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-f7m5-5x7g-2p52
- github.com https://github.com/umbraco/Umbraco-CMS/security/advisories/GHSA-f7m5-5x7g-2p52