Skip to content
Noroxi
NVD / CVE Program· CNA GitHub_M

CVE-2025-54425: Umbraco's Delivery API allows for cached requests to be returned with an invalid API key

MediumCVSS 5.3 · v3.1—No exploit Fix available

Noroxi assessment

Priority: Monitor (action score 21/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.39% (FIRST EPSS).
  • Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
  • According to CISA the attack is automatable: targets can be found by mass scanning.
  • Fixed version: Umbraco.Cms.Api.Delivery (NuGet) 13.9.3, 15.4.4, 16.1.1.

Low priority for now. Upgrade to Umbraco.Cms.Api.Delivery (NuGet) 13.9.3, 15.4.4, 16.1.1 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

Published
Jul 30, 2025
Updated
Jun 17, 2026
EPSS
0.3% · 33th percentile

Report tools

JSON

Action score

21

Monitor

Low priority for now.

CVSS
21 / 40 · 5.3 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.3%

CISA SSVC decision

Exploitation
none
Automatable
yes
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
—
CNA · GitHub_M
5.3
NVD has not scored this yet; the score shown is the CNA’s.

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2025-54425

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • CVE alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools, at most 30 a day (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools
Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
umbracoumbraco cms

Versions reported by the vendor

Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.

  • umbraco Umbraco-CMS

    • >= 13.0.0, < 13.9.3, >= 15.0.0, < 15.4.4, >= 16.0.0, < 16.1.1affected

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • umbraco umbraco cms13.0.0 and later · before 13.9.3
  • umbraco umbraco cms15.0.0 and later · before 15.4.4
  • umbraco umbraco cms16.0.0 and later · before 16.1.1

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
NuGetUmbraco.Cms.Api.Deliveryfrom 13.0.0 · before 13.9.313.9.3
NuGetUmbraco.Cms.Api.Deliveryfrom 15.0.0 · before 15.4.415.4.4
NuGetUmbraco.Cms.Api.Deliveryfrom 16.0.0 · before 16.1.116.1.1

Other highest-scoring records for the same primary product.

  • CVE-2012-10054Umbraco CMS < 4.7.1 codeEditorSave.asmx RCE
    60This week
  • CVE-2025-67288An arbitrary file upload vulnerability in Umbraco CMS v16.3.3 allows attackers to execute arbitrary code by uploading a crafted PDF file.
    40Plan
  • CVE-2020-5810A stored XSS vulnerability exists in Umbraco CMS <= 8.9.1 or current.
    40Plan

Published before and after this one in the same product

  • ← EarlierCVE-2025-48953Jun 3, 2025 · Umbraco Vulnerable to By-Pass of Configured Allowed Extensions for File Uploads
    26Monitor
  • ← EarlierCVE-2025-49147Jun 24, 2025 · Umbraco.Cms Vulnerable to Disclosure of Configured Password Requirements
    21Monitor
  • Later →CVE-2025-66625Dec 9, 2025 · Umbraco Vulnerable to Improper File Access and Credential Exposure through Dictionary Import Functionality
    19Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
NuGet:Umbraco.Cms.Api.Delivery13.9.3Package registry (OSV)
NuGet:Umbraco.Cms.Api.Delivery15.4.4Package registry (OSV)
NuGet:Umbraco.Cms.Api.Delivery16.1.1Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

  • CVE-2025-24011190 days apartUmbraco CMS Vulnerable to User Enumeration Feasible Based On Management API Timing and Response Codes
    21Monitor
  • CVE-2025-66625132 days apartUmbraco Vulnerable to Improper File Access and Credential Exposure through Dictionary Import Functionality
    19Monitor

Not on record for this CVE: EPSS history · researcher credit · public bounty program.

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • No account or password is required.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
low · data can be read
Integrity
none
Availability
none
Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality impact
Low
Integrity impact
None
Availability impact
None

CVSS vector

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

nvd-secondary

Root cause

The extension requests broader permissions than its function needs and sends the data it collects out for purposes beyond its stated function.

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

json
{  "permissions": ["tabs", "<all_urls>"],  "background": { "service_worker": "analytics.js" }}

Fixed

json
{  "permissions": ["activeTab"],  "host_permissions": ["https://yildiz.example/*"]}

References

All records