GHSA-7jxj-rpx7-ph2c — Umbraco.Forms
LOWGHSA-7jxj-rpx7-ph2c is a low-severity (CVSS 3.1) vulnerability in Umbraco.Forms. A fix is available for Umbraco.Forms — see the affected versions and patch details below.
Umbraco.Forms CDN may cache sensitive form uploads when processed by ImageSharp
Real-World Exposure
Umbraco.Forms.NETUmbraco.Forms.NETUmbraco.FormsReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects NuGet packages — download data is not available via public APIs for these ecosystems.
Description
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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| .NETNuGet | Umbraco.Forms | all versions | 13.9.0dotnet add package Umbraco.Forms --version 13.9.0 |
| .NETNuGet | Umbraco.Forms | ≥ 14.0.0-beta001&&< 16.4.0 | 16.4.0dotnet add package Umbraco.Forms --version 16.4.0 |
| .NETNuGet | Umbraco.Forms | ≥ 17.0.0-rc1&&< 17.1.0 | 17.1.0dotnet add package Umbraco.Forms --version 17.1.0 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for Umbraco.Forms, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update Umbraco.Forms to 13.9.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-7jxj-rpx7-ph2c is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-7jxj-rpx7-ph2c can be triaged on real exposure rather than presence alone.
Tailored to GHSA-7jxj-rpx7-ph2c. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-7jxj-rpx7-ph2c in your dependencies?
O3 Security finds GHSA-7jxj-rpx7-ph2c across NuGet dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.