CVE-2025-54425

Umbraco's Delivery API allows for cached requests to be returned with an invalid API key

Published Jul 30, 2025 CVSS 3.1 · 5.3 Medium EPSS < 1% KEV · Not listed
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.

Remediation

No solution or workaround provided in the CVE record

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
EUVD EUVD EUVD-2025-23164 Umbraco Delivery API allows for cached requests to be returned with an invalid API key
Github GHSA Github GHSA GHSA-75vq-qvhr-7ffr Umbraco Delivery API allows for cached requests to be returned with an invalid API key
History
Type Values Removed Values Added
CPEs cpe:2.3:a:umbraco:umbraco_cms:*:*:*:*:*:*:*:*
Type Values Removed Values Added
First Time appeared Umbraco
Umbraco umbraco Cms
Vendors & Products Umbraco
Umbraco umbraco Cms
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
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.
Title Umbraco's Delivery API allows for cached requests to be returned with an invalid API key
Weaknesses CWE-200
References
Metrics cvssV3_1

{'score': 5.3, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N'}

Weaknesses

Sources

Status
PUBLISHED
Assigner
GitHub_M
Published
Updated
Jul 30, 2025, 2:06 PM
Reserved
Jul 21, 2025, 11:18 PM
Status
Analyzed
Published
Jul 30, 2025, 2:15 PM
Modified
Jun 17, 2026, 9:40 AM