CVE Details
Basic Information
| Title | Umbraco’s Delivery API allows for cached requests to be returned with an invalid API key |
|---|---|
| Type | cve |
| Published | 2025-07-30T13:41:07.799Z |
| Modified | 2025-07-30T14:06:12.115Z |
Product Information
| Vendor | umbraco |
|---|---|
| Product | Umbraco-CMS |
| Version | >= 13.0.0, < 13.9.3 |
CVSS Information
| Base Score | 5.3 (MEDIUM) |
|---|---|
| Attack Vector | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N |
Affected Products
- umbraco Umbraco-CMS >= 13.0.0, < 13.9.3
- umbraco Umbraco-CMS >= 15.0.0, < 15.4.4
- umbraco Umbraco-CMS >= 16.0.0, < 16.1.1
Additional Information
| CWE List | CWE-200 |
|---|---|
| Source | GitHub_M |
Description
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.
References
- https://github.com/umbraco/Umbraco-CMS/security/advisories/GHSA-75vq-qvhr-7ffr
- https://github.com/umbraco/Umbraco-CMS/commit/7e82c258eebaa595eadc9b000461e27d02bc030e
- https://github.com/umbraco/Umbraco-CMS/commit/9f37db18d11c8ba4e3ecdeb35291af30ebee7cd0
- https://github.com/umbraco/Umbraco-CMS/commit/da43086017e1e318f6b5373391d78421efebce3a
- https://docs.umbraco.com/umbraco-cms/reference/content-delivery-api