CVE-2025-54425 – umbraco.cms.api.delivery

Package

Manager: nuget
Name: umbraco.cms.api.delivery
Vulnerable Version: >=13.0.0 <13.9.3 || >=15.0.0 <15.4.4 || >=16.0.0 <16.1.1

Severity

Level: Medium

CVSS v3.1: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

CVSS v4.0: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N

EPSS: 0.00044 pctl0.12818

Details

Umbraco Delivery API allows for cached requests to be returned with an invalid API key ### Impact Umbraco's [content delivery API](https://docs.umbraco.com/umbraco-cms/reference/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

Metadata

Created: 2025-07-29T19:10:39Z
Modified: 2025-07-30T15:42:05Z
Source: https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2025/07/GHSA-75vq-qvhr-7ffr/GHSA-75vq-qvhr-7ffr.json
CWE IDs: ["CWE-200"]
Alternative ID: GHSA-75vq-qvhr-7ffr
Finding: F308
Auto approve: 1