NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
.NET
.NET NuGet
Not in CISA KEV
NONE severity

Using the directory back payload (“/../”) in a package name allows placement of package in other foldersGHSA-6324-52pr-h4p5

NONE

GHSA-6324-52pr-h4p5 is a none-severity (CVSS 0) Path Traversal vulnerability in Umbraco.CMS. A fix is available for Umbraco.CMS — see the affected versions and patch details below.

Also known asCVE-2023-49089
Published
Updated
Affected
3 pkgs
Patched
3 / 3
Exploits
None indexed
Exploitation data as of Nov 6, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
0.6%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs50th percentile — riskier than 50% of all scored CVEsHighest risk
0.00%0.37%0.75%1.12%0.1%0.6%May 26Sep 26Nov 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

3 pkgs affected
.NETUmbraco.CMS.NETUmbraco.CMS.NETUmbraco.CMS

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects NuGet packages — download data is not available via public APIs for these ecosystems.

Description

Umbraco is an ASP.NET content management system (CMS). Starting in version 8.0.0 and prior to versions 8.18.10, 10.8.1, and 12.3.0, Backoffice users with permissions to create packages can use path traversal and thereby write outside of the expected location. Versions 8.18.10, 10.8.1, and 12.3.0 contain a patch for this issue.

Affected Packages

3 total 3 fixed
EcosystemPackageVulnerable rangeFix
.NETNuGetUmbraco.CMS≥ 8.0.0&&< 8.18.108.18.10dotnet add package Umbraco.CMS --version 8.18.10
.NETNuGetUmbraco.CMS≥ 9.0.0&&< 10.8.110.8.1dotnet add package Umbraco.CMS --version 10.8.1
.NETNuGetUmbraco.CMS≥ 11.0.0&&< 12.3.412.3.4dotnet add package Umbraco.CMS --version 12.3.4

Affected Products

1 product · 3 configurations
Application
umbraco cmsumbraco
≥ 12.0.0 && < 12.3.0
range

Detection & mitigation playbook

Open-source dependency

  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for Umbraco.CMS, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update Umbraco.CMS to 8.18.10 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-6324-52pr-h4p5 is resolved across your whole dependency graph.

  3. Workarounds

    Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.

Frequently Asked Questions

#### Impact Backoffice users with permissions to create packages can use path traversal and thereby write outside of the expected location. #### Explanation of the vulnerability The “Package” section in Umbraco Backoffice allows a logged in user to write folders outside of the default package directory.
O3 Security · Impact-Aware SCA

Is GHSA-6324-52pr-h4p5 in your dependencies?

Find it across NuGet, including transitive dependencies.

Scan my dependencies How O3 SCA works
Using the directory back payload (“/../”) in a package…