NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
.NET
.NET NuGet
Not in CISA KEV
MEDIUM severity

CVE-2025-23041 — Umbraco.Forms

MEDIUM

CVE-2025-23041 is a medium-severity (CVSS 5.8) Improper Input Validation vulnerability in Umbraco.Forms. A fix is available for Umbraco.Forms — see the affected versions and patch details below.

Umbraco Forms's Short and Long Answer Fields Are Not Validated Server-Side For Maximum Length

Published
Updated
Affected
4 pkgs
Patched
4 / 4
Exploits
None indexed
Exploitation data as of Nov 9, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

  • CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
  • CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2025-23041.

EPSS Exploitation Probability

via FIRST.org ↗
0.4%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs33th percentile — riskier than 33% of all scored CVEsHighest risk
0.00%0.30%0.59%0.89%0.2%0.4%May 26Sep 26Nov 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

4 pkgs affected
.NETUmbraco.Forms.NETUmbracoForms.NETUmbraco.Forms.NETUmbraco.Forms

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.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.

Affected Packages

4 total 4 fixed
EcosystemPackageVulnerable rangeFix
.NETNuGetUmbraco.Formsall versions10.5.7dotnet add package Umbraco.Forms --version 10.5.7
.NETNuGetUmbracoFormsall versions8.13.16dotnet add package UmbracoForms --version 8.13.16
.NETNuGetUmbraco.Forms≥ 11.0.0-rc1&&< 13.2.213.2.2dotnet add package Umbraco.Forms --version 13.2.2
.NETNuGetUmbraco.Forms≥ 14.0.0-beta001&&< 14.1.214.1.2dotnet add package Umbraco.Forms --version 14.1.2

Affected Products

1 product · 4 configurations
Application
umbraco formsumbraco
≥ 14.0.0 && < 14.1.2
range

Detection & mitigation playbook

Open-source dependency

  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for Umbraco.Forms, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

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

  3. 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.

Frequently Asked Questions

### Impact Character limits configured by editors for short and long answer fields are validated only client-side, not server-side. ### Patches Patched in 8.13.16, 10.5.7, 13.2.2, 14.1.2
O3 Security · Impact-Aware SCA

Is CVE-2025-23041 in your dependencies?

Find it across NuGet, including transitive dependencies.

Scan my dependencies How O3 SCA works
CVE-2025-23041: Umbraco.Forms — Fixed in 10.5.7