Quick answers
- Is This vulnerability exploited in the wild?
- No. Junglewise Threat Intelligence has no report of This vulnerability being exploited in the wild.
- How severe is This vulnerability?
- Medium severity, with a CVSS score of 5.3, published 19 June 2026.
- Which products and versions are affected?
- Riganti DotVVM < 4.2.11, > 4.3.0-preview01-final, < 4.3.15, >= 5.0.0-preview01-final, < 5.0.0-preview09-final.
- Is there a fix for This vulnerability?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is This vulnerability attacked?
- It is attacked over the network, in a software library.
- Am I affected?
- Check whether anything you run is named in the advisory. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
An unrestricted file upload vulnerability (CWE-434) exists in DotVVM when file upload storage is configured. The framework previously allowed any network-based attacker to upload files without requiring a cryptographic token or specific authorization. This can be exploited to perform a Denial of Service (DoS) attack by filling the server's storage capacity. The issue is resolved in versions 4.2.11, 4.3.15, and 5.0.0-preview09 by requiring a cryptographic token generated by the FileUpload component for all upload requests. Additionally, a new configuration option 'AuthorizeFileUpload' has been introduced to allow developers to restrict upload capabilities to specific authorized users.
Affected products
- Riganti DotVVM < 4.2.11, > 4.3.0-preview01-final, < 4.3.15, >= 5.0.0-preview01-final, < 5.0.0-preview09-final
Timeline
- 2026-06-18: disclosed: Advisory published by maintainer
- 2026-06-19: advisory: GitHub Advisory published