How severe is CVE-2025-54425?

CVE-2025-54425 has a CVSS score of 5.3/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2025-54425?

CVE-2025-54425 affects the following packages: Umbraco.Cms.Api.Delivery (NuGet), Umbraco.Cms.Api.Delivery (NuGet), Umbraco.Cms.Api.Delivery (NuGet). Ecosystems affected: NuGet.

How do I fix CVE-2025-54425?

Update Umbraco.Cms.Api.Delivery to 13.9.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-54425 is resolved across your whole dependency graph.

How do I detect CVE-2025-54425 in my NuGet dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for Umbraco.Cms.Api.Delivery, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2025-54425 if there is no patch (or I can't update yet)?

Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.

Is CVE-2025-54425 actively exploited in the wild?

No public exploit code has been indexed for CVE-2025-54425 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2025-54425?

CVE-2025-54425 has an EPSS (Exploit Prediction Scoring System) score of 0.4%, placing it in the 33th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2025-54425?

CVE-2025-54425 is classified as Information Exposure (CWE-200). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2025-54425 published, and has it been updated?

CVE-2025-54425 was published on July 30, 2025 and was last updated on October 28, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

.NET

.NET NuGet

Not in CISA KEV

MEDIUM severity

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

MEDIUMFix: umbraco/Umbraco-CMS@7e82c25

CVE-2025-54425 is a medium-severity (CVSS 5.3) Information Exposure vulnerability in Umbraco.Cms.Api.Delivery. A fix is available for Umbraco.Cms.Api.Delivery — see the affected versions and patch details below.

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

Also known asGHSA-75vq-qvhr-7ffr

Published

Jul 30, 2025

Updated

Oct 28, 2026

Affected

3 pkgs

Patched

3 / 3

Exploits

None indexed

Exploitation data as of Nov 6, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2025-54425.

EPSS Exploitation Probability

via FIRST.org ↗

0.4%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs33th percentile — riskier than 33% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

3 pkgs affected

.NETUmbraco.Cms.Api.Delivery.NETUmbraco.Cms.Api.Delivery.NETUmbraco.Cms.Api.Delivery

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects NuGet packages — download data is not available via public APIs for these ecosystems.

Description

Impact

Umbraco's 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

Affected Packages

3 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
.NETNuGet	`Umbraco.Cms.Api.Delivery`	≥ 13.0.0&&< 13.9.3	13.9.3`dotnet add package Umbraco.Cms.Api.Delivery --version 13.9.3`
.NETNuGet	`Umbraco.Cms.Api.Delivery`	≥ 15.0.0&&< 15.4.4	15.4.4`dotnet add package Umbraco.Cms.Api.Delivery --version 15.4.4`
.NETNuGet	`Umbraco.Cms.Api.Delivery`	≥ 16.0.0&&< 16.1.1	16.1.1`dotnet add package Umbraco.Cms.Api.Delivery --version 16.1.1`

Affected Products

1 product · 3 configurations

Application

umbraco cmsumbraco

≥ 16.0.0 && < 16.1.1

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for Umbraco.Cms.Api.Delivery, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update Umbraco.Cms.Api.Delivery to 13.9.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-54425 is resolved across your whole dependency graph.
Workarounds
Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.

Frequently Asked Questions

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