# CVE-2025-32017: Umbraco has a Management API Vulnerability to Path Traversal With Authenticated Users

> Authenticated users can exploit a path traversal vulnerability in the management API to upload files to incorrect locations.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 8 Apr 2025
- **Updated:** 9 Apr 2025
- **Also known as:** GHSA-q62r-8ppj-xvf4

## What is CVE-2025-32017?

CVE-2025-32017 is a high-severity path traversal vulnerability in Umbraco Umbraco Cms, published on 8 Apr 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Umbraco is a free and open source .NET content management system. 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. The issue affects Umbraco 14+ and is patched in 14.3.4 and 15.3.1.

Weakness: CWE-23 (Relative Path Traversal)

## Which versions are affected by CVE-2025-32017?

4 open source packages ship an affected version, including Umbraco.Cms. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `Umbraco.Cms` | NuGet | From 14.0.0--preview004 | 14.3.4 |
| `Umbraco.Cms` | NuGet | From 14.0.0--preview004 | 14.3.4 |
| `Umbraco.Cms` | NuGet | From 15.0.0-rc1 | 15.3.1 |
| `Umbraco.Cms` | NuGet | From 15.0.0-rc1 | 15.3.1 |

Products: Umbraco Umbraco Cms.

## How do I fix CVE-2025-32017?

Upgrade Umbraco.Cms to a fixed version for your release line: 14.3.4 or 15.3.1.

## Is CVE-2025-32017 being exploited?

There is no known exploitation of CVE-2025-32017 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-2020-9471](https://insights.sbomify.com/CVE-2020-9471/): Umbraco CMS Authenticated File Upload (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-32017 and fix it if it is affected.

What it is: CVE-2025-32017 is a high-severity path traversal vulnerability in Umbraco Umbraco Cms, published on 8 Apr 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-32017 in the wild and no public exploit code.

Affected packages and fixed versions:
- Umbraco.Cms (NuGet): affected from 14.0.0--preview004; fixed in 14.3.4
- Umbraco.Cms (NuGet): affected from 14.0.0--preview004; fixed in 14.3.4
- Umbraco.Cms (NuGet): affected from 15.0.0-rc1; fixed in 15.3.1
- Umbraco.Cms (NuGet): affected from 15.0.0-rc1; fixed in 15.3.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-32017/ (Markdown: https://insights.sbomify.com/CVE-2025-32017/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-32017
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-32017
- OSV: https://osv.dev/vulnerability/CVE-2025-32017

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-32017/
Summaries are generated and may contain mistakes; the official description above is the record.