How severe is CVE-2024-43377?

CVE-2024-43377 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 CVE-2024-43377?

CVE-2024-43377 affects the following packages: Umbraco.Cms (NuGet). Ecosystems affected: NuGet.

How do I fix CVE-2024-43377?

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

How do I detect CVE-2024-43377 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 CVE-2024-43377 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 CVE-2024-43377?

O3 pinpoints whether CVE-2024-43377 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 CVE-2024-43377 actively exploited in the wild?

No public exploit code has been indexed for CVE-2024-43377 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 CVE-2024-43377?

CVE-2024-43377 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 CVE-2024-43377 published, and has it been updated?

CVE-2024-43377 was published on August 20, 2024 and was last updated on July 15, 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 NuGet

CVE-2024-43377

MEDIUM

CVE-2024-43377 is a medium-severity (CVSS 5.4) CWE-284 vulnerability in Umbraco.Cms. O3 Security confirms whether CVE-2024-43377 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 asGHSA-hrww-x3fq-xcvh

Published

Aug 20, 2024

Updated

Jul 15, 2026

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

Umbraco CMS is an ASP.NET CMS. An authenticated user can access a few unintended endpoints. This issue is fixed in 14.1.2.

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 CVE-2024-43377 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 CVE-2024-43377 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 CVE-2024-43377. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

Umbraco CMS is an ASP.NET CMS. An authenticated user can access a few unintended endpoints. This issue is fixed in 14.1.2.

O3 Security · Impact-Aware SCA

Is CVE-2024-43377 in your dependencies?

O3 detects CVE-2024-43377 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