Home Cyber Security News Umbraco CMS Vulnerability Could Allow Privilege Escalation

Umbraco CMS Vulnerability Could Allow Privilege Escalation

by Abeerah Hashim
Umbraco CMS vulnerability

A serious vulnerability has been discovered in the Umbraco CMS, that allowed an adversary to gain admin-level privileges. Users should update the CMS to the latest version as it includes the fix.

Umbraco CMS Vulnerability

Security researchers from Trustwave have found a serious vulnerability in Umbraco CMS. Exploiting the bug could allow an adversary to gain elevated privileges on the target system.

Specifically, the vulnerability resided in an API endpoint due to improper user verification. Thus, any low privileged user could gain admin privileges.

As described in an advisory,

There is an [sic] privilege escalation issue in the core administrative screens which allow a low privileged user to access various resources otherwise limited to higher privileged users.  The issue exists in an API endpoint which does not properly check the user’s authorization prior to returning results found in the application’s logging section.

Thus, any authenticated user with low privileges could view the application logs in the core administrative screens. According to Trustwave, the risk of this information leak relied on the extent of information in the logs.

Note that the risk of the information leak will be contextualized based on what is actually logged by default or by whatever additional logging the application maintainer has decided to add.  For example, custom logging of a failed authentication routine could potentially leak usernames and passwords to the log.

Trustwave has also shared the details of this exploit in their post.

Patches Rolled Out

The researchers found the vulnerability affecting the Umbraco version 8.9.0 (also seen in 8.6.3). Whereas, Umbraco version 7.x remained unaffected by this bug.

Upon discovering this flaw in the CMS, the researchers disclosed the vulnerability to the vendors in November 2020.

Consequently, Umbraco deployed the fixes with Umbraco CMS 8.10.0 in December 2020. Though, Trustwave has clarified that they have not verified the patches.

Since the fixes are out, users must ensure updating their CMS to the latest version to avoid a potential information leak.

You may also like

Latest Hacking News

Privacy Preference Center


The __cfduid cookie is used to identify individual clients behind a shared IP address and apply security settings on a per-client basis.

cookie_notice_accepted and gdpr[allowed_cookies] are used to identify the choices made from the user regarding cookie consent.

For example, if a visitor is in a coffee shop where there may be several infected machines, but the specific visitor's machine is trusted (for example, because they completed a challenge within your Challenge Passage period), the cookie allows Cloudflare to identify that client and not challenge them again. It does not correspond to any user ID in your web application, and does not store any personally identifiable information.

__cfduid, cookie_notice_accepted, gdpr[allowed_cookies]


DoubleClick by Google refers to the DoubleClick Digital Marketing platform which is a separate division within Google. This is Google’s most advanced advertising tools set, which includes five interconnected platform components.

DoubleClick Campaign Manager: the ad-serving platform, called an Ad Server, that delivers ads to your customers and measures all online advertising, even across screens and channels.

DoubleClick Bid Manager – the programmatic bidding platform for bidding on high-quality ad inventory from more than 47 ad marketplaces including Google Display Network.

DoubleClick Ad Exchange: the world’s largest ad marketplace for purchasing display, video, mobile, Search and even Facebook inventory.

DoubleClick Search: is more powerful than AdWords and used for purchasing search ads across Google, Yahoo, and Bing.

DoubleClick Creative Solutions: for designing, delivering and measuring rich media (video) ads, interactive and expandable ads.



The _ga is asssociated with Google Universal Analytics - which is a significant update to Google's more commonly used analytics service. This cookie is used to distinguish unique users by assigning a randomly generated number as a client identifier. It is included in each page request in a site and used to calculate visitor, session and campaign data for the sites analytics reports. By default it is set to expire after 2 years, although this is customisable by website owners.

The _gat global object is used to create and retrieve tracker objects, from which all other methods are invoked. Therefore the methods in this list should be run only off a tracker object created using the _gat global variable. All other methods should be called using the _gaq global object for asynchronous tracking.

_gid works as a user navigates between web pages, they can use the gtag.js tagging library to record information about the page the user has seen (for example, the page's URL) in Google Analytics. The gtag.js tagging library uses HTTP Cookies to "remember" the user's previous interactions with the web pages.

_ga, _gat, _gid