How severe is GHSA-hrww-x3fq-xcvh?

GHSA-hrww-x3fq-xcvh has a CVSS score of 5.4/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-hrww-x3fq-xcvh?

GHSA-hrww-x3fq-xcvh affects the following packages: Umbraco.Cms (NuGet). Ecosystems affected: NuGet.

How do I fix GHSA-hrww-x3fq-xcvh?

Update Umbraco.Cms to 14.1.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-hrww-x3fq-xcvh is resolved across your whole dependency graph.

How do I detect GHSA-hrww-x3fq-xcvh in my NuGet dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for Umbraco.Cms. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-hrww-x3fq-xcvh 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-hrww-x3fq-xcvh?

O3 pinpoints whether GHSA-hrww-x3fq-xcvh is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-hrww-x3fq-xcvh actively exploited in the wild?

No public exploit code has been indexed for GHSA-hrww-x3fq-xcvh 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 type of vulnerability is GHSA-hrww-x3fq-xcvh?

GHSA-hrww-x3fq-xcvh is classified as CWE-284 (CWE-284). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-hrww-x3fq-xcvh published, and has it been updated?

GHSA-hrww-x3fq-xcvh was published on August 20, 2024 and was last updated on September 17, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

.NET NuGet

GHSA-hrww-x3fq-xcvh

MEDIUM

GHSA-hrww-x3fq-xcvh is a medium-severity (CVSS 5.4) CWE-284 vulnerability in Umbraco.Cms. O3 Security confirms whether GHSA-hrww-x3fq-xcvh is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Umbraco CMS Improper Access Control vulnerability

Also known asCVE-2024-43377

Published

Aug 20, 2024

Updated

Sep 17, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Blast Radius

1 pkg affected

.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

As an authenticated user one can access a few unintended endpoints

Explanation of the vulnerability

Few endpoints in Umbraco Management API was not protected by a specific section. These just required you to be authenticated. Due to the fact that a member is also just authenticated, it was possible to get info from these endpoints using a member token.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
.NETNuGet	`Umbraco.Cms`	≥ 14.0.0&&< 14.1.2	14.1.2

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. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update Umbraco.Cms to 14.1.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-hrww-x3fq-xcvh 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 pinpoints whether GHSA-hrww-x3fq-xcvh is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-hrww-x3fq-xcvh. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Impact As an authenticated user one can access a few unintended endpoints ### Explanation of the vulnerability Few endpoints in Umbraco Management API was not protected by a specific section. These just required you to be authenticated. Due to the fact that a member is also just authenticated, it was possible to get info from these endpoints using a member token.

O3 Security · Impact-Aware SCA

Is GHSA-hrww-x3fq-xcvh in your dependencies?

O3 detects GHSA-hrww-x3fq-xcvh across NuGet dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works