# CVE-2024-35239: Stored Cross-site Scripting on Components of Umbraco Forms

> Authenticated users can inject unsafe HTML into Umbraco Forms components, enabling stored XSS attacks unless unsafe rendering is disabled.

- **Severity:** Low 2.7 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 28 May 2024
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-p572-p2rj-q5f4

## What is CVE-2024-35239?

CVE-2024-35239 is a low-severity cross-site scripting vulnerability in Umbraco.Forms.Issues, published on 28 May 2024. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Umbraco Commerce is an open source dotnet web forms solution. In affected versions an authenticated user that has access to edit Forms may inject unsafe code into Forms components. This issue can be mitigated by configuring TitleAndDescription:AllowUnsafeHtmlRendering after upgrading to one of the patched versions (13.0.1, 12.2.2, 10.5.3, 8.13.13).

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

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

8 open source packages ship an affected version, including Umbraco.Forms. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `Umbraco.Forms` | NuGet | From 10.0.0 | 10.5.3 |
| `Umbraco.Forms` | NuGet | From 10.0.0 | 10.5.3 |
| `Umbraco.Forms` | NuGet | From 12.0.0 | 12.2.2 |
| `Umbraco.Forms` | NuGet | From 12.0.0 | 12.2.2 |
| `Umbraco.Forms` | NuGet | From 13.0.0 | 13.0.1 |
| `Umbraco.Forms` | NuGet | From 13.0.0 | 13.0.1 |
| `Umbraco.Forms` | NuGet | From 8.0.0 | 8.13.13 |
| `Umbraco.Forms` | NuGet | From 8.0.0 | 8.13.13 |

Products: Umbraco Umbraco Forms.

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

Upgrade Umbraco.Forms to a fixed version for your release line: 10.5.3, 12.2.2, 13.0.1 or 8.13.13.

## Is CVE-2024-35239 being exploited?

There is no known exploitation of CVE-2024-35239 in the wild and no public exploit code.

## Other vulnerabilities in Umbraco.Forms.Issues

- [CVE-2021-33224](https://insights.sbomify.com/CVE-2021-33224/): File upload in n/a (critical 9.8)
- [CVE-2025-68924](https://insights.sbomify.com/CVE-2025-68924/): UmbracoForms Vulnerable to Remote Code Execution via Untrusted WSDL Compilation in Dynamic SOAP Client Generation (high 7.5)
- [CVE-2026-24687](https://insights.sbomify.com/CVE-2026-24687/): Umbraco.Forms has path traversal and file enumeration vulnerability in Linux/Mac (medium 6.0)
- [CVE-2025-23041](https://insights.sbomify.com/CVE-2025-23041/): Short and Long Answer Fields Are Not Validated Server-Side For Maximum Length in Umbraco.Forms (medium 5.8)
- [CVE-2020-7685](https://insights.sbomify.com/CVE-2020-7685/): Insecure Defaults (medium 5.4)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-35239 is a low-severity cross-site scripting vulnerability in Umbraco.Forms.Issues, published on 28 May 2024. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-35239 in the wild and no public exploit code.

Affected packages and fixed versions:
- Umbraco.Forms (NuGet): affected from 10.0.0; fixed in 10.5.3
- Umbraco.Forms (NuGet): affected from 10.0.0; fixed in 10.5.3
- Umbraco.Forms (NuGet): affected from 12.0.0; fixed in 12.2.2
- Umbraco.Forms (NuGet): affected from 12.0.0; fixed in 12.2.2
- Umbraco.Forms (NuGet): affected from 13.0.0; fixed in 13.0.1
- Umbraco.Forms (NuGet): affected from 13.0.0; fixed in 13.0.1
- Umbraco.Forms (NuGet): affected from 8.0.0; fixed in 8.13.13
- Umbraco.Forms (NuGet): affected from 8.0.0; fixed in 8.13.13

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

## Sources

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

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