CVE-2025-54425: Umbraco's 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
Other sources
Umbraco is an ASP.NET CMS. In versions 13.0.0 through 13.9.2, 15.0.0 through 15.4.1 and 16.0.0 through 16.1.0, the content delivery API can be restricted from public access where 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, where 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. This is fixed in versions 13.9.3, 15.4.4 and 16.1.1.
— MITRE
Affected Software
Remediation
Event History
Frequently Asked Questions
What is the severity of CVE-2025-54425?
CVE-2025-54425 has been classified with a high severity due to its potential impact on unauthorized access to Umbraco's content delivery API.
How do I fix CVE-2025-54425?
To fix CVE-2025-54425, update Umbraco.Cms.Api.Delivery to version 16.1.1, 15.4.4, or 13.9.3 or later, depending on your current version.
Which versions are affected by CVE-2025-54425?
CVE-2025-54425 affects Umbraco.Cms.Api.Delivery versions from 16.0.0 to 16.1.0, from 15.0.0 to 15.4.3, and from 13.0.0 to 13.9.2.
What are the consequences of not addressing CVE-2025-54425?
Failing to address CVE-2025-54425 may lead to unauthorized access to sensitive data via the content delivery API.
Is an API key required for CVE-2025-54425 mitigation?
Yes, implementing an API key in the header is necessary for mitigating CVE-2025-54425 when accessing the content delivery API.