Skip to content

Umbraco has a Management API Vulnerability to Path Traversal With Authenticated Users

High severity GitHub Reviewed Published Apr 8, 2025 in umbraco/Umbraco-CMS • Updated Apr 9, 2025

Package

nuget Umbraco.Cms (NuGet)

Affected versions

>= 14.0.0--preview004, < 14.3.4
>= 15.0.0-rc1, < 15.3.1

Patched versions

14.3.4
15.3.1

Description

Impact

Authenticated users to the Umbraco backoffice are able to craft management API request that exploit a path traversal vulnerability to upload files into a incorrect location.

Patches

The issue affects Umbraco 14+ and is patched in 14.3.4 and 15.3.1.

Workarounds

Umbraco supports the configuration of allowed and disallowed file extensions. Using these options to allow only necessary file extensions significantly reduces the scope of the vulnerability.

References

@AndyButland AndyButland published to umbraco/Umbraco-CMS Apr 8, 2025
Published by the National Vulnerability Database Apr 8, 2025
Published to the GitHub Advisory Database Apr 9, 2025
Reviewed Apr 9, 2025
Last updated Apr 9, 2025

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

EPSS score

Exploit Prediction Scoring System (EPSS)

This score estimates the probability of this vulnerability being exploited within the next 30 days. Data provided by FIRST.
(20th percentile)

Weaknesses

CVE ID

CVE-2025-32017

GHSA ID

GHSA-q62r-8ppj-xvf4

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.