CVE-2026-24687: Umbraco.Forms.Issues · Path Traversal
Affects Umbraco.Forms.IssuesSource CVE Database V5
Not known to be exploited · CVSS 6.0 Medium : upgrade to 17.1.1 or 16.4.1 when convenient.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 39% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 17.1.1, 16.4.1
CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 29 Jan 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.
What to do
Upgrade Umbraco.Forms.Issues to 17.1.1 or 16.4.1.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| umbracoUmbraco.Forms.Issues | Affected
| Fixed in
|
NuGetumbraco.forms.issuespkg:nuget/umbraco.forms.issuesOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
1. Upgrade Umbraco Forms to versions 16.4.1 or 17.1.1 immediately to apply the official patch. 2. If upgrading is delayed, configure Web Application Firewalls (WAFs) or reverse proxies to detect and block path traversal sequences such as '../' and '..\' in the fileName parameter of the /umbraco/forms/api/v1/export endpoint. 3. Restrict network access to the Umbraco backoffice interface by implementing IP whitelisting or VPN access to limit authenticated user exposure. 4. Disable or block the /umbraco/forms/api/v1/export endpoint entirely if the export functionality is not required in the deployment. 5. Enforce strong authentication and monitor backoffice user activity for unusual file access patterns. 6. Conduct regular security audits and vulnerability scans on Umbraco installations, especially on Mac/Linux servers. 7. Educate administrators on the risks of path traversal and the importance of patch management.
Description
Umbraco Forms is a form builder that integrates with the Umbraco content management system. It's possible for an authenticated backoffice-user to enumerate and traverse paths/files on the systems filesystem and read their contents, on Mac/Linux Umbraco installations using Forms. As Umbraco Cloud runs in a Windows environment, Cloud users aren't affected. This issue affects versions 16 and 17 of Umbraco Forms and is patched in 16.4.1 and 17.1.1. If upgrading is not immediately possible, users can mitigate this vulnerability by configuring a WAF or reverse proxy to block requests containing path traversal sequences (`../`, `..\`) in the `fileName` parameter of the export endpoint, restricting network access to the Umbraco backoffice to trusted IP ranges, and/or blocking the `/umbraco/forms/api/v1/export` endpoint entirely if the export feature is not required. However, upgrading to the patched version is strongly recommended.