# CVE-2024-43376: Umbraco CMS vulnerable to Generation of Error Message Containing Sensitive Information

> Attackers can obtain sensitive stack trace information from Umbraco CMS Management API endpoints, potentially aiding further attacks.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N`)
- **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:** 20 Aug 2024
- **Updated:** 20 Aug 2024
- **Also known as:** GHSA-77gj-crhp-3gvx

## What is CVE-2024-43376?

CVE-2024-43376 is a medium-severity vulnerability in Umbraco Umbraco Cms, published on 20 Aug 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Umbraco is an ASP.NET CMS. Some endpoints in the Management API can return stack trace information, even when Umbraco is not in debug mode. This vulnerability is fixed in 14.1.2.

Weakness: CWE-209 (Generation of Error Message Containing Sensitive Information)

## Which versions are affected by CVE-2024-43376?

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `Umbraco.Cms.Api.Management` | NuGet | From 14.0.0 | 14.1.2 |
| `Umbraco.Cms.Api.Management` | NuGet | From 14.0.0 | 14.1.2 |

Products: Umbraco Umbraco Cms.

## How do I fix CVE-2024-43376?

Upgrade Umbraco.Cms.Api.Management to 14.1.2 or later.

## Is CVE-2024-43376 being exploited?

There is no known exploitation of CVE-2024-43376 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-2025-32017](https://insights.sbomify.com/CVE-2025-32017/): Umbraco has a Management API Vulnerability to Path Traversal With Authenticated Users (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-43376 and fix it if it is affected.

What it is: CVE-2024-43376 is a medium-severity vulnerability in Umbraco Umbraco Cms, published on 20 Aug 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-43376 in the wild and no public exploit code.

Affected packages and fixed versions:
- Umbraco.Cms.Api.Management (NuGet): affected from 14.0.0; fixed in 14.1.2
- Umbraco.Cms.Api.Management (NuGet): affected from 14.0.0; fixed in 14.1.2

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-2024-43376/ (Markdown: https://insights.sbomify.com/CVE-2024-43376/index.md)
```

## Sources

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

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