CVE-2025-23041 — Umbraco.Forms
MEDIUMCVE-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
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
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
How urgent is this, really
CVE-2025-23041 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 378,156 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
Umbraco.Forms.NETUmbracoForms.NETUmbraco.Forms.NETUmbraco.FormsReal-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
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| .NETNuGet | Umbraco.Forms | all versions | 10.5.7dotnet add package Umbraco.Forms --version 10.5.7 |
| .NETNuGet | UmbracoForms | all versions | 8.13.16dotnet add package UmbracoForms --version 8.13.16 |
| .NETNuGet | Umbraco.Forms | ≥ 11.0.0-rc1&&< 13.2.2 | 13.2.2dotnet add package Umbraco.Forms --version 13.2.2 |
| .NETNuGet | Umbraco.Forms | ≥ 14.0.0-beta001&&< 14.1.2 | 14.1.2dotnet add package Umbraco.Forms --version 14.1.2 |
Detection & mitigation playbook
Open-source dependencyDetect
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.
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.
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.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2025-23041 can be triaged on real exposure rather than presence alone.
Tailored to CVE-2025-23041. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2025-23041 in your dependencies?
O3 Security finds CVE-2025-23041 across NuGet dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.