CVE-2025-54425
Umbraco's Delivery API allows for cached requests to be returned with an invalid API key
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.
Attack profile
How easy it is to exploit
- Attack vector
- Network
- Complexity
- Low
- Privileges needed
- None
- User interaction
- None
What an attacker can affect
- Confidentiality
- Low
- Integrity
- None
- Availability
- None
Exploit likelihood
What each source reports
CVE List Score used
Umbraco's Delivery API allows for cached requests to be returned with an invalid API key
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.
- Record
CVE-2025-54425- CVSS 3.1
- 5.3 Medium
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N - Weakness
- CWE-200
- Updated
- 2026-11-02
EUVDEUVD-2025-23164
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.
- Record
EUVD-2025-23164- CVSS 3.1
- 5.3 Medium
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N - Updated
- 2026-11-02
GitHub AdvisoriesGHSA-75vq-qvhr-7ffr
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
- Record
GHSA-75vq-qvhr-7ffr- CVSS 3.1
- 5.3 Medium
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N - Weakness
- CWE-200
- Updated
- 2026-11-02
NVD
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.
- Record
CVE-2025-54425- CVSS 3.1
- 5.3 Medium
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N - Weakness
- CWE-200
- Updated
- 2026-11-02
OSV
Umbraco's Delivery API allows for cached requests to be returned with an invalid API key
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.
- Record
CVE-2025-54425- CVSS 3.1
- 5.3 Medium
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N - Weakness
- CWE-200
- Updated
- 2026-11-02
OSVGHSA-75vq-qvhr-7ffr
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
- Record
GHSA-75vq-qvhr-7ffr- CVSS 3.1
- 5.3 Medium
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N - Weakness
- CWE-200
- Updated
- 2026-11-02
Affected products
Affected packages
| Package | Affected | Fixed |
|---|---|---|
Umbraco.Cms.Api.DeliveryNuGet |
13.0.0 to 13.9.2 | 13.9.3 |
Umbraco.Cms.Api.DeliveryNuGet |
15.0.0 to 15.4.3 | 15.4.4 |
Umbraco.Cms.Api.DeliveryNuGet |
16.0.0 to 16.1.0 | 16.1.1 |
Umbraco.Cms.Api.DeliveryNuGet |
13.0.0 up to 13.9.3, plus listed versions 13.0.113.0.213.0.313.1.013.1.0-rc Show 32 moreShow less13.1.113.2.013.2.0-rc13.2.113.2.213.3.013.3.0-rc13.3.113.3.213.4.013.4.0-rc13.4.0-rc213.4.113.5.013.5.0-rc13.5.113.5.213.5.313.6.013.6.0-rc13.6.0-rc213.7.013.7.0-rc13.7.113.7.213.8.013.8.0-rc13.8.113.9.013.9.0-rc13.9.113.9.2 |
13.9.3 |
Umbraco.Cms.Api.DeliveryNuGet |
15.0.0 up to 15.4.4, plus listed versions 15.1.015.1.0-rc15.1.0-rc215.1.115.1.2 Show 15 moreShow less15.2.015.2.0-rc15.2.115.2.215.2.315.3.015.3.0-rc15.3.0-rc215.3.115.4.015.4.0-rc15.4.0-rc215.4.115.4.215.4.3 |
15.4.4 |
Umbraco.Cms.Api.DeliveryNuGet |
16.0.0 up to 16.1.1, plus listed versions 16.1.016.1.0-rc |
16.1.1 |
History
| Recorded | Changed | Sources |
|---|---|---|
| first indexed | CVE List, EUVD, GitHub Advisories, NVD, OSV |
Dates are when Every CVE recorded each change. Upstream dates may differ.
In short
CVE-2025-54425 is a medium vulnerability (CVSS 5.3) in Umbraco Cms, published July 29, 2025. No source lists public exploit code. EPSS puts the chance of exploitation in the next 30 days at 0.39%, the 33rd percentile. Fixed in Umbraco.Cms.Api.Delivery 13.9.3.
References
github.com/umbraco/Umbraco-CMS/security/advisories/GHSA-75vq-qvhr-7ffr
docs.umbraco.com/umbraco-cms/reference/content-delivery-api
nvd.nist.gov/vuln/detail/CVE-2025-54425