Security Advisory: Security Patches for Umbraco CMS, Umbraco Workflow, Umbraco Commerce, Umbraco Engage, and Umbraco MCP Server SDK now available

We recommend upgrading to the secure versions

Anders Nis Herforth Larsen
Written by Anders Nis Herforth Larsen

Seven vulnerabilities - five classified as high and two as moderate - have been found and fixed across Umbraco CMS, Umbraco Workflow, Umbraco Commerce, Umbraco Engage, and the Umbraco MCP Server SDK. Today, we have released patches for the affected products and recommend upgrading.

What’s affected?

Umbraco CMS

Moderate Severity (GHSA-5pr6-xx84-wp49)

Affected Product Version Range:

  • 12.x (End-of-Life, see below)

  • 13.0.0 - 13.16.4

  • 14.0.0 - 15.4.4 (End-of-Life, see below)

Moderate Severity (GHSA-348f-9mg8-rhv4)

Affected Product Version Range:

  • 17.4.0 - 17.8.1

  • 18.0.0 - 18.3.1

Umbraco Workflow

High Severity (GHSA-vw5g-jmgg-hw78, GHSA-7457-w8c8-jh29)

Affected Product Version Range:

  • 13.0.0 - 13.5.4

  • 14.x - 16.x (End-of-Life, see below)

  • 17.0.0 - 17.5.4

  • 18.0.0 - 18.2.5

Umbraco Commerce

High Severity (GHSA-cw69-92rj-fp3r)

Affected Product Version Range:

  • 13.0.0 - 13.3.3

  • 14.x - 16.x (End-of-Life, see below)

  • 17.0.0 - 17.2.12

  • 18.0.0 - 18.1.12

  • 19.0.0-rc.1

Umbraco Engage

High Severity (GHSA-gq5w-hprc-q59x)

Affected Product Version Range:

  • 13.0.0 - 13.8.2

  • 16.0.0 - 16.3.3 (End-of-Life, see below)

  • 17.0.0 - 17.5.0

  • 18.0.0 - 18.2.0

Umbraco MCP Server SDK

High Severity (GHSA-9hv2-2794-vp6f)

Affected Product Version Range:

  • @umbraco-cms/mcp-hosted 17.0.0-beta.5 - 17.0.0-beta.29

  • @umbraco-cms/mcp-hosted 1.0.0-beta.30 - 1.0.0-beta.47

How to fix the vulnerabilities

If you’re using a supported version of the affected products, you are able to upgrade to a new patch version of these releases the way you would normally upgrade.

Patched versions:

  • Umbraco CMS: 13.16.5, 17.8.2 and 18.3.2

  • Umbraco Workflow: 13.5.5, 17.6.0 and 18.3.0

  • Umbraco Commerce: 13.3.4, 17.2.13, 18.1.13 and 19.0.0-rc.2

  • Umbraco Engage: 13.8.3, 17.6.0 and 18.3.0

  • Umbraco MCP Server SDK: @umbraco-cms/mcp-hosted 1.0.0-beta.48

After upgrading:

  • Umbraco CMS 17 and 18: rebuild the Members index from the Examine Management dashboard in the Settings section.

  • Umbraco Workflow: check that custom user groups have the Workflow permissions their users need.

  • Umbraco Commerce: if you can’t rule out misuse by a backoffice user, rotate the payment gateway secret keys and webhook signing secrets stored in your payment methods.

How do you check which version you are on? Reach out to your technical contact for your Umbraco site with this blog post, and they will be able to take care of the necessary precautions.

If your project is on Umbraco Cloud

If your Umbraco project is hosted on Umbraco Cloud, an automatic upgrade will be rolled out today to fix the vulnerabilities for Umbraco CMS. On Umbraco CMS 17 and 18, you still need to rebuild the members index once your project has been upgraded, as described above. If you’re running Umbraco Workflow, Umbraco Commerce or Umbraco Engage on your Cloud project(s), these fixes need to be implemented manually, as they’re add-ons to your Umbraco Cloud setup. A hosted MCP server built on the Umbraco MCP Server SDK runs outside Umbraco Cloud, so it also needs to be upgraded manually.

If you cannot upgrade immediately

Upgrading is the only complete fix. Until you can upgrade, you can reduce your exposure:

  • Umbraco CMS (Delivery API): if you don’t use the Delivery API, keep it disabled. If only your own server-side applications use it, turn off public access and require an API key.

  • Umbraco CMS (members index): add backoffice users who have access to both the Settings and Members sections to the Sensitive data user group, or remove one of those sections from their user groups. Make sure custom code that queries the members index only returns the fields it needs.

  • Umbraco Workflow, Umbraco Commerce and Umbraco Engage: limit backoffice accounts to users you trust and remove accounts that are no longer needed. For Umbraco Workflow, also review approval group membership and recent approvals.

  • Umbraco MCP Server SDK: limit MCP client registration to clients you trust, and ask backoffice users not to open unexpected links while signed in to the backoffice.

What if I’m on an unsupported/ EOL version?

Unsupported versions can be subject to these vulnerabilities, but will not receive a patch. This includes Umbraco CMS 12, 14 and 15, Umbraco Workflow and Umbraco Commerce 14, 15 and 16, and Umbraco Engage 16. If you are running a version that is past End-of-Life, the recommended path is to upgrade to a supported major version - Umbraco 17 (LTS) or Umbraco 18. You can check the support status of your version on our Long-term Support and End-of-Life page.

What we know about the vulnerabilities

Umbraco CMS: Protected content exposed through the Delivery API

The fix for CVE-2026-69197 didn’t cover every case. In Umbraco CMS 13, the Delivery API could still return content protected with Public Access, or content of types excluded from the Delivery API, when that content is referenced through a Content Picker or Multi-Node Tree Picker.

Only sites with the Delivery API enabled (it’s disabled by default) that reference protected or excluded content this way are affected. No login is required if the Delivery API is publicly accessible. Umbraco CMS 17 and 18 are not affected.

The severity of this vulnerability is: Moderate. It can expose protected content without a login.

Umbraco CMS: Sensitive member data visible through the members index

Since Umbraco CMS 17.4.0, the values of member properties marked as sensitive have been stored in the members search index. Backoffice users with access to the Settings and Members sections could read these values through Examine Management, even if they weren’t in the Sensitive data user group.

Sites are only affected if member properties are marked as sensitive and backoffice users have access to both the Settings and Members sections without being in the Sensitive data group, or if custom code returns all fields from the members index. The values can be read, but not changed.

The severity of this vulnerability is: Moderate. It requires a backoffice login with access to specific sections.

Umbraco Workflow: Content approval could be bypassed

Parts of the Umbraco Workflow backoffice API didn’t check the user’s Workflow permissions. Any backoffice user could change approval groups and Workflow settings, read workflow history, and approve changes that were waiting for approval.

Sites are affected if they give backoffice accounts to users who aren’t meant to manage Workflow, such as editors who should only submit changes for approval. A backoffice login is required.

The severity of this vulnerability is: High. It lets backoffice users bypass the approval process.

Umbraco Workflow: SQL injection in backoffice searches

Some Umbraco Workflow searches and filters in the backoffice, and the history cleanup settings, didn’t pass user input safely to the database. A backoffice user could use this to read data from the site’s Umbraco database and, depending on the database permissions, change it.

All sites running an affected version of Umbraco Workflow are affected. A backoffice login is required, but not administrator rights.

The severity of this vulnerability is: High. It gives any backoffice user access to data across the Umbraco database.

Umbraco Commerce: Store data exposed to backoffice users without access

Parts of the Umbraco Commerce backoffice API didn’t check whether the user had access to the Commerce section or to the store in question. Any backoffice user could view customer data, gift cards and payment method settings, including payment gateway secret keys. Users limited to one store could also view and change orders, payments and gift cards in other stores.

Sites are affected if they have backoffice users who aren’t meant to see Commerce data, such as content editors, or if they limit Commerce users to specific stores. A backoffice login is required.

The severity of this vulnerability is: High. It exposes payment secrets and shoppers’ personal data to backoffice users without Commerce access.

Umbraco Engage: Engage and content permissions could be bypassed

Parts of the Umbraco Engage backoffice API didn’t check the user’s Engage permissions, which were only applied in the backoffice screens. Any backoffice user could view visitor analytics and visitor profiles, including the names and email addresses of members linked to them, and change Engage’s tests, personalization and settings. Some Engage functions could also remove content prepared for tests and personalization, or publish pending changes to a page (in versions 17.5.0 and 18.2.0 only), without the matching content permission.

Sites are affected if they have backoffice users who aren’t meant to have full access to Engage, member data or publishing. By default, Engage gives every user group access to all its features, so on sites that never restricted Engage, the extra access is limited to member data and content changes. A backoffice login is required.

The severity of this vulnerability is: High. It exposes visitor profiles, including members’ names and email addresses, and lets backoffice users change what Engage serves to site visitors.

Umbraco MCP Server SDK: Unapproved MCP clients could connect

The consent step of the hosted MCP server (@umbraco-cms/mcp-hosted) didn’t check that an approval came from the user who was shown the consent screen. If a signed-in backoffice user opened a link or page controlled by an attacker, an unknown MCP client could get access acting as that user.

Only sites running a hosted MCP server built on @umbraco-cms/mcp-hosted, including servers created from the project template, are affected. The attacker doesn’t need an account, but a backoffice user with a current sign-in has to open their link.

The severity of this vulnerability is: High. The MCP client can read and change whatever that backoffice user can.

Credit

We’d like to thank ozataknurullah and KToskana for reporting the Umbraco CMS Delivery API vulnerability, BL4CK570RM for reporting the Umbraco CMS members index vulnerability, Lucas Teste from Soluss for reporting the Umbraco Workflow content approval vulnerability, and mattbrailsford for reporting the Umbraco Commerce vulnerability.

Any questions?

If you have any questions or comments about this advisory, make sure to get in touch with us through the dedicated security email address listed at https://umbraco.com/security. Here you can also find information on how we handle security-related issues.

For direct communication related to security in Umbraco products, please sign up for the dedicated security mailing list.