Umbraco.Forms.Issues up to 8.13.15/10.5.6/13.2.1/14.1.1 denial of service
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.4 | $0-$5k | 0.00 |
Summary
A vulnerability has been found in Umbraco.Forms.Issues up to 8.13.15/10.5.6/13.2.1/14.1.1 and classified as problematic. The affected element is an unknown function. This manipulation causes denial of service. This vulnerability is tracked as CVE-2025-23041. The attack is possible to be carried out remotely. No exploit exists. The affected component should be upgraded. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Details
A vulnerability has been found in Umbraco.Forms.Issues up to 8.13.15/10.5.6/13.2.1/14.1.1 and classified as problematic. Affected by this vulnerability is an unknown part. The manipulation with an unknown input leads to a denial of service vulnerability. The CWE definition for the vulnerability is CWE-404. The product does not release or incorrectly releases a resource before it is made available for re-use. As an impact it is known to affect availability. The summary by CVE is:
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.
It is possible to read the advisory at github.com. This vulnerability is known as CVE-2025-23041 since 01/10/2025. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. The technical details are unknown and an exploit is not publicly available. The attack technique deployed by this issue is T1499 according to MITRE ATT&CK.
Upgrading to version 8.13.16, 10.5.7, 13.2.2 or 14.1.2 eliminates this vulnerability.
The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2025-0070). Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Name
Version
- 8.13.0
- 8.13.1
- 8.13.2
- 8.13.3
- 8.13.4
- 8.13.5
- 8.13.6
- 8.13.7
- 8.13.8
- 8.13.9
- 8.13.10
- 8.13.11
- 8.13.12
- 8.13.13
- 8.13.14
- 8.13.15
- 10.5.0
- 10.5.1
- 10.5.2
- 10.5.3
- 10.5.4
- 10.5.5
- 10.5.6
- 13.2.0
- 13.2.1
- 14.1.0
- 14.1.1
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.5VulDB Meta Temp Score: 5.4
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
VulDB Vector: 🔍
VulDB Reliability: 🔍
CNA Base Score: 5.8
CNA Vector (GitHub_M): 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
Exploiting
Class: Denial of serviceCWE: CWE-404
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: Umbraco.Forms.Issues 8.13.16/10.5.7/13.2.2/14.1.2
Timeline
01/10/2025 🔍01/14/2025 🔍
01/14/2025 🔍
09/20/2025 🔍
Sources
Advisory: GHSA-9v8m-qv22-f268Status: Confirmed
CVE: CVE-2025-23041 (🔍)
GCVE (CVE): GCVE-0-2025-23041
GCVE (VulDB): GCVE-100-291847
EUVD: 🔍
Entry
Created: 01/14/2025 10:55 PMUpdated: 09/20/2025 06:09 PM
Changes: 01/14/2025 10:55 PM (63), 09/20/2025 06:09 PM (1)
Complete: 🔍
Cache ID: 244:498:40
No comments yet. Languages: en.
Please log in to comment.