Umbraco.Engage.Forms Allows Unauthorized Access to Multiple API Endpoints

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

7.5 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

EPSS

• CVE-2026-27449: 0.41% estimated exploitation activity in the next 30 days; percentile 35.13 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

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…

Published by the source

27 Feb 2026, 18:35 UTC

Last modified by the source

19 Mar 2026, 16:13 UTC

Source last checked

26 Oct 2026, 17:04 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-86vq-ccwf-rm62

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-27449

Advisory: Umbraco.Engage.Forms Allows Unauthorized Access to Multiple API Endpoints
IDs: CVE-2026-27449, GHSA-86vq-ccwf-rm62
Record: https://patchnext.com/advisories/cve-2026-27449 (revision 1, source checked 26 Oct 2026, 17:04 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: umbraco.engage.forms 17.1.1, 16.2.1. A vendor fix does not mean a deployment is fixed.

## Affected components
- NuGet umbraco.engage.forms: affected >= 17.0.0, < 17.1.1; >= 16.0.0, < 16.2.1; fixed in 16.2.1, 17.1.1

## Suggested inspection (read-only)
- NuGet umbraco.engage.forms: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on umbraco.engage.forms.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-86vq-ccwf-rm62 (GitHub-reviewed advisory GHSA-86vq-ccwf-rm62 lists affected ranges: NuGet umbraco.engage.forms >=17.0.0 =16.0.0 <16.2.1)

Commands are suggestions: review each one before running it.