Advisory record · GHSA-75vq-qvhr-7ffr

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

CVSS 5.3 MediumEPSS 0.0039 · 33rd percentile

Published by the GitHub Advisory Database at 29 Jul 2025, 19:10 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
Umbraco.Cms.Api.DeliveryNuGet>=13.0.0, <13.9.3 || >=15.0.0, <15.4.4 || >=16.0.0, <16.1.113.9.3, 15.4.4, 16.1.1
Identifiers
GHSA-75vq-qvhr-7ffr · CVE-2025-54425
Weakness (CWE)
CWE-200
Published
29 Jul 2025
Updated
30 Jul 2025

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Umbraco.Cms.Api.Delivery versions from 13.0.0 before 13.9.3, from 15.0.0 before 15.4.4, and from 16.0.0 before 16.1.1 are affected. When the Delivery API is restricted by API key and output caching is enabled, cached responses are not varied by the API key header, so a request without a valid key can receive a cached response that a keyed request produced earlier. Upgrade to 13.9.3, 15.4.4, or 16.1.1. As a workaround, remove output caching from the Delivery API or shorten its cache period, or restrict access to the Delivery API by other means such as IP address.

Written 9 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
5.3 Medium 3.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0039, the 33rd percentile, on 11 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 29 Jul 2025, 05:13 UTC Published by the maintainers as a GitHub repository advisory
  2. 31 Oct 2026, 15:22 UTC First seen by agentprime
  3. 31 Oct 2026, 15:22 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.