cve.bz

CVE-2025-54425 umbraco umbraco cms

5.3 mediumEPSS 0.4%Fix available

Medium (5.3) in umbraco umbraco cms. EPSS 0.4% estimated probability of exploitation activity in the next 30 days. Fixed in Umbraco.Cms.Api.Delivery 13.9.3, 15.4.4, 16.1.1.

On this page
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.

Severity

CVSS 3.1

5.3 medium
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
EPSS
0.4% (unchanged from 0.4% a week ago; 0.4% 30 days ago) estimated probability of exploitation activity in the next 30 days; 34th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: yes · Technical impact: partial, assessed 2025-07-30. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2025-54425 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2025-54425?via=ask-ai-copy and https://cve.bz/cve/CVE-2025-54425?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2025-54425 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
umbraco:umbraco_cmsfrom 13.0.0 before 13.9.3
umbraco:umbraco_cmsfrom 15.0.0 before 15.4.4
umbraco:umbraco_cmsfrom 16.0.0 before 16.1.1

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-75vq-qvhr-7ffrNuGetUmbraco.Cms.Api.Delivery>=13.0.0 <13.9.313.9.3
GHSA-75vq-qvhr-7ffrNuGetUmbraco.Cms.Api.Delivery>=15.0.0 <15.4.415.4.4
GHSA-75vq-qvhr-7ffrNuGetUmbraco.Cms.Api.Delivery>=16.0.0 <16.1.116.1.1

Attack patterns (CAPEC)

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-200 (59).

References

Check your stackJSON