Loading...
Skip to main content

CVE-2025-54425 — Vulnerability in Umbraco.Cms.Api.Delivery — CVE...

MEDIUM

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

Published July 29, 2025Updated July 30, 2025Source: osv

Summary

### 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

Advisory Timeline

  • First published July 29, 2025 (440 days ago).
  • Last revised July 30, 2025 — 1 day after initial publication.

Remediation

Upgrade to the fixed version using your package manager.

NuGet
Update Umbraco.Cms.Api.Delivery to 15.4.4 or later
dotnet add package Umbraco.Cms.Api.Delivery --version 15.4.4
NuGet
Update Umbraco.Cms.Api.Delivery to 16.1.1 or later
dotnet add package Umbraco.Cms.Api.Delivery --version 16.1.1
NuGet
Update Umbraco.Cms.Api.Delivery to 13.9.3 or later
dotnet add package Umbraco.Cms.Api.Delivery --version 13.9.3

After upgrading, run your dependency scanner again to confirm the vulnerability is resolved.

Affected Packages (3)

Affects 1 ecosystem: nuget (1).

PackageEcosystemAffectedFixed In
Umbraco.Cms.Api.Delivery
nuget
15.0.0, 15.1.0, 15.1.0-rc, 15.1.0-rc2 (+17 more)15.4.4
Umbraco.Cms.Api.Delivery
nuget
16.0.0, 16.1.0, 16.1.0-rc16.1.1
Umbraco.Cms.Api.Delivery
nuget
13.0.0, 13.0.1, 13.0.2, 13.0.3 (+34 more)13.9.3

Vulnerability Classification

Common Weakness Enumeration (CWE) identifiers for this vulnerability type.

  • CWE-200
    Information ExposureMITRE

CVSS Score Breakdown

What the CVSS (Common Vulnerability Scoring System) 5.3 score means for each attack dimension.

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

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

Frequently Asked Questions

What is CVE-2025-54425?
Umbraco Delivery API allows for cached requests to be returned with an invalid API key This vulnerability has been assigned a severity rating of MEDIUM (CVSS score: 5.3/10).
How do I check if my project is affected by CVE-2025-54425?
CVE-2025-54425 affects Umbraco.Cms.Api.Delivery. Use GeekWala's free vulnerability scanner to check your dependencies against CVE-2025-54425 and 200,000+ other known vulnerabilities.

Severity & Exploitability

CVSS Score
5.3

Exploitation requires specific conditions or has limited impact. Remediate within weeks.

Also Known As

GHSA-75vq-qvhr-7ffr

Related CVEs

  • CVE-2026-106111
    MEDIUM

    ImageSharp: EXR ZIP decoder can expose stale allocator data after a short inflate

  • CVE-2026-65829
    MEDIUM

    MPXJ: Potential Path Traversal Vulnerability in Primavera P3 PRX and SureTrak STX readers

Check if you're affected

Scan your dependencies to see if this vulnerability affects your projects.

Scan Your Dependencies