# CVE-2025-23041: Short and Long Answer Fields Are Not Validated Server-Side For Maximum Length in Umbraco.Forms

> Attackers can submit oversized form data bypassing client-side limits, potentially causing denial of service in Umbraco Forms applications.

- **Severity:** Medium 5.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 14 Jan 2025
- **Updated:** 14 Jan 2025
- **Also known as:** GHSA-9v8m-qv22-f268

## What is CVE-2025-23041?

CVE-2025-23041 is a medium-severity vulnerability in Umbraco.Forms.Issues, published on 14 Jan 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Umbraco.Forms is a web form framework written for the nuget ecosystem. Character limits configured by editors for short and long answer fields are validated only client-side, not server-side. This issue has been patched in versions 8.13.16, 10.5.7, 13.2.2, and 14.1.2. Users are advised to upgrade. There are no known workarounds for this issue.

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2025-23041?

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `Umbraco.Forms` | NuGet | All versions | 10.5.7 |
| `Umbraco.Forms` | NuGet | All versions | 10.5.7 |
| `Umbraco.Forms` | NuGet | From 11.0.0-rc1 | 13.2.2 |
| `Umbraco.Forms` | NuGet | From 11.0.0-rc1 | 13.2.2 |
| `Umbraco.Forms` | NuGet | From 14.0.0-beta001 | 14.1.2 |
| `Umbraco.Forms` | NuGet | From 14.0.0-beta001 | 14.1.2 |
| `UmbracoForms` | NuGet | All versions | 8.13.16 |
| `UmbracoForms` | NuGet | All versions | 8.13.16 |

Products: Umbraco Umbraco Forms.

## How do I fix CVE-2025-23041?

Upgrade Umbraco.Forms to a fixed version for your release line: 10.5.7, 13.2.2 or 14.1.2.

## Is CVE-2025-23041 being exploited?

There is no known exploitation of CVE-2025-23041 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-2020-7685](https://insights.sbomify.com/CVE-2020-7685/): Insecure Defaults (medium 5.4)
- [CVE-2024-35239](https://insights.sbomify.com/CVE-2024-35239/): Stored Cross-site Scripting on Components of Umbraco Forms (low 2.7)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-23041 and fix it if it is affected.

What it is: CVE-2025-23041 is a medium-severity vulnerability in Umbraco.Forms.Issues, published on 14 Jan 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-23041 in the wild and no public exploit code.

Affected packages and fixed versions:
- Umbraco.Forms (NuGet): affected all versions; fixed in 10.5.7
- Umbraco.Forms (NuGet): affected all versions; fixed in 10.5.7
- Umbraco.Forms (NuGet): affected from 11.0.0-rc1; fixed in 13.2.2
- Umbraco.Forms (NuGet): affected from 11.0.0-rc1; fixed in 13.2.2
- Umbraco.Forms (NuGet): affected from 14.0.0-beta001; fixed in 14.1.2
- Umbraco.Forms (NuGet): affected from 14.0.0-beta001; fixed in 14.1.2
- UmbracoForms (NuGet): affected all versions; fixed in 8.13.16
- UmbracoForms (NuGet): affected all versions; fixed in 8.13.16

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

## Sources

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

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