# CVE-2024-47819: Umbraco CMS vulnerable to stored Cross-site Scripting in the "dictionary name" on Dictionary section

> Attackers can inject malicious scripts into dictionary names, potentially escalating privileges or taking over admin accounts in Umbraco CMS.

- **Severity:** Medium 4.2 (`CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 22 Oct 2024
- **Updated:** 22 Oct 2024
- **Also known as:** GHSA-c5g6-6xf7-qxp3

## What is CVE-2024-47819?

CVE-2024-47819 is a medium-severity cross-site scripting vulnerability in Umbraco Umbraco Cms, published on 22 Oct 2024. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

Umbraco, a free and open source .NET content management system, has a cross-site scripting vulnerability starting in version 14.0.0 and prior to versions 14.3.1 and 15.0.0. This can be leveraged to gain access to higher-privilege endpoints, e.g. if you get a user with admin privileges to run the code, you can potentially elevate all users and grant them admin privileges or access protected content. Versions 14.3.1 and 15.0.0 contain a patch. As a workaround, ensure that access to the Dictionary section is only granted to trusted users.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

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

4 open source packages ship an affected version, including Umbraco.Cms.StaticAssets and @umbraco-cms/backoffice. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `Umbraco.Cms.StaticAssets` | NuGet | From 14.0.0 | 14.3.1 |
| `Umbraco.Cms.StaticAssets` | NuGet | From 14.0.0 | 14.3.1 |
| `@umbraco-cms/backoffice` | npm | From 14.0.0 | 14.3.1 |
| `@umbraco-cms/backoffice` | npm | From 14.0.0 | 14.3.1 |

Products: Umbraco Umbraco Cms.

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

Upgrade Umbraco.Cms.StaticAssets to 14.3.1 or later.

## Is CVE-2024-47819 being exploited?

There is no known exploitation of CVE-2024-47819 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-47819 and fix it if it is affected.

What it is: CVE-2024-47819 is a medium-severity cross-site scripting vulnerability in Umbraco Umbraco Cms, published on 22 Oct 2024. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2024-47819 in the wild and no public exploit code.

Affected packages and fixed versions:
- Umbraco.Cms.StaticAssets (NuGet): affected from 14.0.0; fixed in 14.3.1
- Umbraco.Cms.StaticAssets (NuGet): affected from 14.0.0; fixed in 14.3.1
- @umbraco-cms/backoffice (npm): affected from 14.0.0; fixed in 14.3.1
- @umbraco-cms/backoffice (npm): affected from 14.0.0; fixed in 14.3.1

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

## Sources

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

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