GHSA-2RM3-333W-XVC4

Workarounds

As a workaround, you can temporarily disable file upload by removing AddUploadedFileStorage or AddDefaultTempStorage from your DotVVM configuration.

Even with the patch, we recommend configuring file upload to use a dedicated partition with limited size.

References

• DotVVM file upload configuration: https://www.dotvvm.com/docs/4.0/pages/concepts/upload-and-download-files/upload-files

All users of DotVVM with configured file upload storage are affected.

DotVVM allows anyone to upload files to the application, potentially causing denial of service by filling the disk.

The application accepts file uploads without adequately restricting the file type or content. Typical impact: remote code execution if the uploaded file can be served and executed on the server.

GHSA-2RM3-333W-XVC4 has a CVSS score of 5.3 (Medium). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (4.2.11, 4.3.15, 5.0.0-preview09-final); upgrading removes the vulnerable code path.

Kodem intelligence

Since version 4.3.15, 4.2.11 and 5.0.0-preview09, DotVVM requires all file upload request to have a cryptographic token, which is automatically generated by the FileUpload component. This means that users without access to any page with the FileUpload component cannot upload any files.

The patch also add the DotvvmConfiguration.Security.AuthorizeFileUpload option which allow you to further restrict which users can upload files.

1. What is GHSA-2RM3-333W-XVC4? GHSA-2RM3-333W-XVC4 is a medium-severity unrestricted upload of dangerous file types vulnerability in DotVVM (nuget), affecting versions < 4.2.11. It is fixed in 4.2.11, 4.3.15, 5.0.0-preview09-final. The application accepts file uploads without adequately restricting the file type or content.
2. How severe is GHSA-2RM3-333W-XVC4? GHSA-2RM3-333W-XVC4 has a CVSS score of 5.3 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of DotVVM are affected by GHSA-2RM3-333W-XVC4? DotVVM (nuget) versions < 4.2.11 is affected.
4. Is there a fix for GHSA-2RM3-333W-XVC4? Yes. GHSA-2RM3-333W-XVC4 is fixed in 4.2.11, 4.3.15, 5.0.0-preview09-final. Upgrade to this version or later.
5. Is GHSA-2RM3-333W-XVC4 exploitable, and should I be worried? Whether GHSA-2RM3-333W-XVC4 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether GHSA-2RM3-333W-XVC4 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix GHSA-2RM3-333W-XVC4?
   • Upgrade DotVVM to 4.2.11 or later
   • Upgrade DotVVM to 4.3.15 or later
   • Upgrade DotVVM to 5.0.0-preview09-final or later