GitHub Advisoryadvisory · NuGet

GHSA-86vq-ccwf-rm62 Umbraco.Engage.Forms Allows Unauthorized Access to Multiple API Endpoints

HIGH Published 2026-02-27 Modified 2026-03-19 Official page ↗
Aliases
CVE-2026-27449
Ecosystem
NuGet
Packages
Umbraco.Engage.Forms
Severity
High
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Weaknesses
CWE-284, CWE-306, CWE-639
Reviewed
2026-02-27

Affected packages

• NuGet Umbraco.Engage.Forms: >= 16.0.0, < 16.2.1 → fixed in 16.2.1 • NuGet Umbraco.Engage.Forms: >= 17.0.0, < 17.1.1 → fixed in 17.1.1

Description

Description A vulnerability has been identified in Umbraco Engage 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. Impact 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. Patches 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 Workarounds _Is there a way for users to fix or remediate the vulnerability without upgrading?_ References _Are there any links users can visit to find out more?_

Related

Alias · CVE (1)

  • CVE-2026-27449 Umbraco Engage is a business intelligence platform. vulnerability

Weakness · CWE (3)

  • CWE-284 Improper Access Control weakness
  • CWE-306 Missing Authentication for Critical Functionality weakness
  • CWE-639 Authorization Bypass Through User-Controlled Key weakness

References