Umbraco.Engage.Forms
Track Umbraco Forms submissions for every visitor and view submitted data within Umbraco Engage
Activity
- Latest release
- 2mo ago
- Total releases
- 20
- Cadence
- ~20 days
- Last 12 months
- 11
Details
- First release
- Oct 22, 2024
| Version | Released | |
|---|---|---|
18.0.0
major
|
18.0.0
major
Dependencies (4)
|
|
18.0.0-rc1
pre
|
18.0.0-rc1
pre
Dependencies (4)
|
|
17.1.2
patch
|
17.1.2
patch
Dependencies (4)
|
|
16.2.2
patch
|
16.2.2
patch
Dependencies (4)
|
|
17.1.1
patch
|
17.1.1
patch
Dependencies (4)
|
|
16.2.1
patch
|
16.2.1
patch
Dependencies (4)
|
|
16.2.0
minor
1 CVE
CVE-2026-27449
GHSA-86vq-ccwf-rm62
Feb 27, 2026
Umbraco.Engage.Forms Allows Unauthorized Access to Multiple API Endpoints
7.5
/ 10
High
Network
Low
None
None
Unchanged
High
None
None
DescriptionA 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. ImpactAn 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. PatchesThe vulnerability affects both v16 and v17. Patches have already been released. Users are advised to update to 16.2.1 or 17.1.1 WorkaroundsIs there a way for users to fix or remediate the vulnerability without upgrading? ReferencesAre there any links users can visit to find out more? Affected versions
16.0.0
16.1.0
16.2.0
17.0.0
17.1.0
Fixed in
16.2.1
17.1.1
References Updated Mar 19, 2026 · Source: OSV.dev |
16.2.0
minor
Dependencies (4)
|
|
17.1.0
minor
1 CVE
CVE-2026-27449
GHSA-86vq-ccwf-rm62
Feb 27, 2026
Umbraco.Engage.Forms Allows Unauthorized Access to Multiple API Endpoints
7.5
/ 10
High
Network
Low
None
None
Unchanged
High
None
None
DescriptionA 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. ImpactAn 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. PatchesThe vulnerability affects both v16 and v17. Patches have already been released. Users are advised to update to 16.2.1 or 17.1.1 WorkaroundsIs there a way for users to fix or remediate the vulnerability without upgrading? ReferencesAre there any links users can visit to find out more? Affected versions
16.0.0
16.1.0
16.2.0
17.0.0
17.1.0
Fixed in
16.2.1
17.1.1
References Updated Mar 19, 2026 · Source: OSV.dev |
17.1.0
minor
Dependencies (4)
|
|
17.0.0
major
1 CVE
CVE-2026-27449
GHSA-86vq-ccwf-rm62
Feb 27, 2026
Umbraco.Engage.Forms Allows Unauthorized Access to Multiple API Endpoints
7.5
/ 10
High
Network
Low
None
None
Unchanged
High
None
None
DescriptionA 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. ImpactAn 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. PatchesThe vulnerability affects both v16 and v17. Patches have already been released. Users are advised to update to 16.2.1 or 17.1.1 WorkaroundsIs there a way for users to fix or remediate the vulnerability without upgrading? ReferencesAre there any links users can visit to find out more? Affected versions
16.0.0
16.1.0
16.2.0
17.0.0
17.1.0
Fixed in
16.2.1
17.1.1
References Updated Mar 19, 2026 · Source: OSV.dev |
17.0.0
major
Dependencies (4)
|
|
16.1.0
minor
1 CVE
CVE-2026-27449
GHSA-86vq-ccwf-rm62
Feb 27, 2026
Umbraco.Engage.Forms Allows Unauthorized Access to Multiple API Endpoints
7.5
/ 10
High
Network
Low
None
None
Unchanged
High
None
None
DescriptionA 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. ImpactAn 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. PatchesThe vulnerability affects both v16 and v17. Patches have already been released. Users are advised to update to 16.2.1 or 17.1.1 WorkaroundsIs there a way for users to fix or remediate the vulnerability without upgrading? ReferencesAre there any links users can visit to find out more? Affected versions
16.0.0
16.1.0
16.2.0
17.0.0
17.1.0
Fixed in
16.2.1
17.1.1
References Updated Mar 19, 2026 · Source: OSV.dev |
16.1.0
minor
Dependencies (4)
|
|
17.0.0-rc1
pre
|
17.0.0-rc1
pre
Dependencies (4)
|
|
16.0.0
major
1 CVE
CVE-2026-27449
GHSA-86vq-ccwf-rm62
Feb 27, 2026
Umbraco.Engage.Forms Allows Unauthorized Access to Multiple API Endpoints
7.5
/ 10
High
Network
Low
None
None
Unchanged
High
None
None
DescriptionA 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. ImpactAn 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. PatchesThe vulnerability affects both v16 and v17. Patches have already been released. Users are advised to update to 16.2.1 or 17.1.1 WorkaroundsIs there a way for users to fix or remediate the vulnerability without upgrading? ReferencesAre there any links users can visit to find out more? Affected versions
16.0.0
16.1.0
16.2.0
17.0.0
17.1.0
Fixed in
16.2.1
17.1.1
References Updated Mar 19, 2026 · Source: OSV.dev |
16.0.0
major
Dependencies (4)
|
|
13.2.0
minor
|
13.2.0
minor
Dependencies (4)
|
|
13.1.1
patch
|
13.1.1
patch
Dependencies (4)
|
|
13.1.0
minor
|
13.1.0
minor
Dependencies (4)
|
|
13.1.0-rc.1
pre
|
13.1.0-rc.1
pre
Dependencies (4)
|
|
13.0.0
initial
|
13.0.0
initial
Dependencies (3)
|
|
13.0.0-rc.3
pre
|
13.0.0-rc.3
pre
Dependencies (3)
|
|
13.0.0-rc.2
pre
|
13.0.0-rc.2
pre
Dependencies (3)
|
|
13.0.0-rc.1
pre
|
13.0.0-rc.1
pre
Dependencies (3)
|