Umbraco.Cms.Api.Delivery
Affected
- introduced
13.0.0, fixed13.9.3(ecosystem)
Fixed versions
13.9.3
Fix
The export has no generic command for this ecosystem.
Advisory
Also known as: CVE-2025-54425
Umbraco Delivery API allows for cached requests to be returned with an invalid API key
Impact
Umbraco's content delivery API can be restricted from public access such that an API key must be provided in a header to authorize the request.
It's also possible to configure output caching, such that the delivery API outputs will be cached for a period of time, improving performance.
There's an issue when these two things are used together though in that the caching doesn't vary by the header that contains the API key. As such it's possible for a user without a valid API key to retrieve a response for a given path and query if it has recently been requested and cached by request with a valid key.
Patches
Patches will be available in 13.9.3, 15.4.4 and 16.1.1.
Workarounds
Workaround is to remove or reduce the time period of the output caching or to provide other restrictions to access the delivery API such as by IP.
References
Content delivery API documentation: https://docs.umbraco.com/umbraco-cms/reference/content-delivery-api
Medium Basis: The source's own band: MODERATE
13.0.0, fixed 13.9.3 (ecosystem)13.9.3
The export has no generic command for this ecosystem.
15.0.0, fixed 15.4.4 (ecosystem)15.4.4
The export has no generic command for this ecosystem.
16.0.0, fixed 16.1.1 (ecosystem)16.1.1
The export has no generic command for this ecosystem.
Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0