Umbraco.Forms CDN may cache sensitive form uploads when processed by ImageSharp
Published 22 Jan 2026 · Updated 3 Feb 2026
Is your project on an affected Umbraco.Forms?
Look after several .NET apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Affected packages
- Affected
- <13.9.0
- Fixed in
- 13.9.0
dotnet add package Umbraco.Forms --version 13.9.0- Affected
- >=14.0.0-beta001 <16.4.0
- Fixed in
- 16.4.0
dotnet add package Umbraco.Forms --version 16.4.0- Affected
- >=17.0.0-rc1 <17.1.0
- Fixed in
- 17.1.0
dotnet add package Umbraco.Forms --version 17.1.0Details
Impact
Protected files uploaded through Umbraco Forms may be served to unauthenticated users when a CDN or caching layer is present and ImageSharp processes the request. ImageSharp sets aggressive cache headers by default, which can cause intermediary caches to store and serve files that should require authentication.
Patches
This issue affects all (supported) versions Umbraco Forms and is patched in 13.9.0, 16.4.0 and 17.1.0.
Workarounds
Add middleware to set cache headers for form uploads. Place the following code in your Startup.cs or Program.cs after app.UseStaticFiles() and any image processing middleware:
app.Use(async (context, next) =>
{
var path = context.Request.Path.Value;
if (!string.IsNullOrEmpty(path) && path.StartsWith("/media/forms/upload/", StringComparison.OrdinalIgnoreCase))
{
context.Response.OnStarting(() =>
{
context.Response.Headers["Cache-Control"] = "private, no-store, no-cache, must-revalidate";
context.Response.Headers["Pragma"] = "no-cache";
context.Response.Headers["Expires"] = "0";
return Task.CompletedTask;
});
}
await next();
});Alternatively, configure your CDN to bypass caching for URLs matching /media/forms/upload/*.
Note: The vulnerability requires:
- A CDN in front of the website
- An authenticated user having previously requested the image
- Knowledge of the form GUID, entry GUID, and image filename
If no CDN is in use, this vulnerability does not apply.
Is GHSA-7jxj-rpx7-ph2c in any of your client repos?
Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected Umbraco.Forms, and gives you the command that fixes it.
More advisories for Umbraco.Forms
- MediumCVE-2026-24687Umbraco.Forms has Path Traversal and File Enumeration Vulnerabilities in Linux/Mac · 30 Jan 2026
- LowCVE-2025-47280Umbraco.Forms has HTML injection vulnerability in 'Send email' workflow · 13 May 2025
- MediumCVE-2025-23041Umbraco Forms's Short and Long Answer Fields Are Not Validated Server-Side For Maximum Length · 14 Jan 2025
- LowCVE-2024-35239Umbraco Forms components vulnerable to Stored Cross-site Scripting · 28 May 2024
References
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.