CVE-2026-27449: Unauthenticated Data Exposure via Broken Access Control in Umbraco Engage

Published: (February 27, 2026 at 02:10 PM EST)
2 min read
Source: Dev.to

Source: Dev.to

Overview

Vulnerability ID: CVE-2026-27449
CVSS v3.1: 7.5 (High)
Published: 2026-02-27

A critical access‑control failure has been identified in Umbraco Engage (formerly uMarketingSuite), specifically affecting the Forms component. The flaw stems from missing authentication and authorization checks on sensitive API endpoints, allowing unauthenticated remote attackers to query proprietary marketing data and form submissions.

By manipulating ID parameters, attackers can perform Insecure Direct Object Reference (IDOR) attacks, enumerating records and leaking business‑intelligence data as well as potentially personally identifiable information (PII).


Technical Details

  • Attack Vector: Network
  • Privileges Required: None
  • Impact: Confidentiality (High)

The vulnerability permits unauthenticated requests to internal Umbraco Engage API endpoints such as /umbraco/.... Successful exploitation results in:

  1. Retrieval of form definitions and submissions.
  2. Access to analytics data tied to marketing campaigns.
  3. Potential exposure of PII stored within form fields.

Affected Versions

ComponentAffected VersionsFixed In
Umbraco.Engage.Forms= 17.0.0, < 17.1.117.1.1

If your environment runs any version prior to the fixed releases, it is vulnerable.


Remediation Steps

  1. Identify the current version of Umbraco.Engage.Forms (or uMarketingSuite) in use.
  2. Update the NuGet package:
    • For 16.x → upgrade to 16.2.1.
    • For 17.x → upgrade to 17.1.1.
  3. Rebuild and redeploy the application to production.
  4. Verify the fix by attempting to access the Engage API endpoints without an active session; the server should now return 401 Unauthorized or a 302 Redirect to the login page.
  5. Additional hardening (recommended):
    • Implement Web Application Firewall (WAF) rules to restrict access to /umbraco/ API paths.
    • Restrict network access to back‑office APIs via VPN or IP allow‑listing.

References


0 views
Back to Blog

Related posts

Read more »