# CVE-2025-54425: Umbraco's Delivery API allows for cached requests to be returned with an invalid API key > Attackers can bypass API key authentication to read cached content if output caching is enabled without varying by the API key header. - **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 30 Jul 2025 - **Updated:** 30 Jul 2025 - **Also known as:** GHSA-75vq-qvhr-7ffr ## What is CVE-2025-54425? CVE-2025-54425 is a medium-severity authentication bypass vulnerability in Umbraco Umbraco Cms, published on 30 Jul 2025. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official 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. Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor) ## Which versions are affected by CVE-2025-54425? 6 open source packages ship an affected version, including Umbraco.Cms.Api.Delivery. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `Umbraco.Cms.Api.Delivery` | NuGet | From 13.0.0 | 13.9.3 | | `Umbraco.Cms.Api.Delivery` | NuGet | From 13.0.0 | 13.9.3 | | `Umbraco.Cms.Api.Delivery` | NuGet | From 15.0.0 | 15.4.4 | | `Umbraco.Cms.Api.Delivery` | NuGet | From 15.0.0 | 15.4.4 | | `Umbraco.Cms.Api.Delivery` | NuGet | From 16.0.0 | 16.1.1 | | `Umbraco.Cms.Api.Delivery` | NuGet | From 16.0.0 | 16.1.1 | Products: Umbraco Umbraco Cms. ## How do I fix CVE-2025-54425? Upgrade Umbraco.Cms.Api.Delivery to a fixed version for your release line: 13.9.3, 15.4.4 or 16.1.1. ## Is CVE-2025-54425 being exploited? There is no known exploitation of CVE-2025-54425 in the wild and no public exploit code. ## Other vulnerabilities in Umbraco Umbraco Cms - [CVE-2025-67288](https://insights.sbomify.com/CVE-2025-67288/): Umbraco CMS has an arbitrary file upload vulnerability (critical 10.0) - [CVE-2014-10074](https://insights.sbomify.com/CVE-2014-10074/): File upload in n/a (critical 9.8) - [CVE-2012-1301](https://insights.sbomify.com/CVE-2012-1301/): Server-side request forgery in n/a (critical 9.8) - [CVE-2012-10054](https://insights.sbomify.com/CVE-2012-10054/): Umbraco CMS < 4.7.1 codeEditorSave.asmx RCE (critical 9.3) - [CVE-2025-32017](https://insights.sbomify.com/CVE-2025-32017/): Umbraco has a Management API Vulnerability to Path Traversal With Authenticated Users (high 8.8) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2025-54425 and fix it if it is affected. What it is: CVE-2025-54425 is a medium-severity authentication bypass vulnerability in Umbraco Umbraco Cms, published on 30 Jul 2025. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: There is no known exploitation of CVE-2025-54425 in the wild and no public exploit code. Affected packages and fixed versions: - Umbraco.Cms.Api.Delivery (NuGet): affected from 13.0.0; fixed in 13.9.3 - Umbraco.Cms.Api.Delivery (NuGet): affected from 13.0.0; fixed in 13.9.3 - Umbraco.Cms.Api.Delivery (NuGet): affected from 15.0.0; fixed in 15.4.4 - Umbraco.Cms.Api.Delivery (NuGet): affected from 15.0.0; fixed in 15.4.4 - Umbraco.Cms.Api.Delivery (NuGet): affected from 16.0.0; fixed in 16.1.1 - Umbraco.Cms.Api.Delivery (NuGet): affected from 16.0.0; fixed in 16.1.1 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2025-54425/ (Markdown: https://insights.sbomify.com/CVE-2025-54425/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2025-54425 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-54425 - OSV: https://osv.dev/vulnerability/CVE-2025-54425 --- From sbomify Insights: https://insights.sbomify.com/CVE-2025-54425/ Summaries are generated and may contain mistakes; the official description above is the record.