How severe is GHSA-6324-52pr-h4p5?

GHSA-6324-52pr-h4p5 has a CVSS score of 0/10, rated NONE. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-6324-52pr-h4p5?

GHSA-6324-52pr-h4p5 affects the following packages: Umbraco.CMS (NuGet), Umbraco.CMS (NuGet), Umbraco.CMS (NuGet). Ecosystems affected: NuGet.

How do I fix GHSA-6324-52pr-h4p5?

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.

How do I detect GHSA-6324-52pr-h4p5 in my NuGet dependencies?

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.

How do I mitigate GHSA-6324-52pr-h4p5 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-6324-52pr-h4p5?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-6324-52pr-h4p5 can be triaged on real exposure rather than presence alone.

Is GHSA-6324-52pr-h4p5 actively exploited in the wild?

No public exploit code has been indexed for GHSA-6324-52pr-h4p5 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-6324-52pr-h4p5?

GHSA-6324-52pr-h4p5 has an EPSS (Exploit Prediction Scoring System) score of 0.6%, placing it in the 49th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-6324-52pr-h4p5?

GHSA-6324-52pr-h4p5 is classified as Path Traversal (CWE-22). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was GHSA-6324-52pr-h4p5 published, and has it been updated?

GHSA-6324-52pr-h4p5 was published on December 13, 2023 and was last updated on September 10, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

.NET

.NET NuGet

Not in CISA KEV

NONE severity

GHSA-6324-52pr-h4p5 — Umbraco.CMS

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.

Using the directory back payload (“/../”) in a package name allows placement of package in other folders.

Also known asCVE-2023-49089

Published

Dec 13, 2023

Updated

Sep 10, 2026

Affected

3 pkgs

Patched

3 / 3

Exploits

None indexed

Exploitation data as of Sep 20, 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 CVEs49th percentile — riskier than 49% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

How urgent is this, really

GHSA-6324-52pr-h4p5 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.

Where this sits among everything scored

Of 377,166 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.

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

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.

Affected Packages

3 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
.NETNuGet	`Umbraco.CMS`	≥ 8.0.0&&< 8.18.10	8.18.10`dotnet add package Umbraco.CMS --version 8.18.10`
.NETNuGet	`Umbraco.CMS`	≥ 9.0.0&&< 10.8.1	10.8.1`dotnet add package Umbraco.CMS --version 10.8.1`
.NETNuGet	`Umbraco.CMS`	≥ 11.0.0&&< 12.3.4	12.3.4`dotnet add package Umbraco.CMS --version 12.3.4`

Detection & mitigation playbook

Open-source dependency

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.
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.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-6324-52pr-h4p5 can be triaged on real exposure rather than presence alone.

Tailored to GHSA-6324-52pr-h4p5. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

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?

O3 Security finds GHSA-6324-52pr-h4p5 across NuGet dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works